Service API Patterns, Protocols, Coupling Types, Metrics > Service API Management Patterns > Proxy Capability

 

Proxy Capability

How can a service subject to decomposition continue to support consumers affected by the decomposition?

Service Decomposition can essentially split a service’s functional boundary into two or more functional boundaries, essentially establishing new services. When this is applied to a service that is already in use, it will clearly impact existing service consumers who have already formed dependencies on the established service.

The Proxy Capability pattern allows an existing service to be remodeled with minimal impact on service consumers. When applying this pattern, capabilities affected by the decomposition are preserved, while those same capabilities are still allowed to become part of the new services. Although the original service’s functional context is changed and its official functional boundary is reduced, it continues to provide capabilities that no longer belong within its context or boundary. These are referred to as proxy capabilities.

 

 

 

 

 

 

 

 

 

By preserving the existing capability and allowing it to act as a proxy for the relocated capability logic, existing consumers will be less impacted.