Service API Proxy


Service API Patterns, Metrics > Fundamental Service API Patterns > Service API Proxy

 

Service API Proxy

How can service consumers be shielded from changes to service APIs

A service consumer can be directly coupled to a published service API. When the service API is changed, the service will no longer function as expected or may no longer be accessible anymore by the service consumer.

The application of the Service API Proxy pattern establishes an intermediate layer of abstraction between the service consumer and a service by introducing a lightweight proxy service that becomes the official endpoint to which the service consumer couples.

This API proxy then acts as a liaison between the service consumer and the service. When the underlying service API changes, the proxy retains its original API to whatever extent possible. It contains logic that accommodates the service API change so that the service consumer remains unaffected.

 

 

 

 

 

 

The service consumer is coupled to the service API proxy. If changes to the underlying service API occur, the API provided by the proxy can remain unchanged, so as to not compromise the service consumer’s dependency on the API.

Module 12: Fundamental Service API Design & Management

This pattern is covered in Module 12: Fundamental Service API Design & Management..

For more information regarding service API design & management courses and accreditation, visit the Service API Specialist program page.