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

 

Distributed Capability

How can a service preserve its functional context while also fulfilling special capability processing requirements?

A service capability originally modeled for a service may end up having unique processing requirements or demands that cannot be accommodated by the service implementation. Separating the service capability logic from the service is not desirable because it will compromise the integrity of the service’s functional context. The Distributed Capability pattern can be applied to preserve the existing functional context while allowing the underlying service capability logic to be physically separated.

 

 

 

 

 

 

 

 

 

 

 

The logic for the Consolidate capability is relocated to a separate physical environment. A service façade component interacts with the consolidation logic on behalf of the Invoice service API.