APIs

Computer to computer interactions (see 2-way certificates for Web Service Security). APIs are tightly integrated into client code – Web Services work through a proxy – nothing from the actual server (except a proxy representation of the service) is needed.  In RESTFul APIs, even the proxy is not really needed  – it is direct HTTP call

State in SOA

– Per Call (new object instantiated for each call) and Per Session (object stays alive for entire session of calls) services.

Operations – 1 way versus Request-Response versus Callbacks  

1-way calls – Fire and Forget

Request Response – Most common pattern

Callbacks 

The client becomes the server – so the client needs to host an HTTP CAllback Object

HTTP cannot be used for callbacks – so WSHTTP and BasicHTTP bindings are both useless (only NetTCP and NamedPipes support Duplex mode)

Anuj holds professional certifications in Google Cloud, AWS as well as certifications in Docker and App Performance Tools such as New Relic. He specializes in Cloud Security, Data Encryption and Container Technologies.

Initial Consultation

Anuj Varma – who has written posts on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

 Twitter Linkedin