|
-
|
Service contracts are standardized to guarantee a baseline measure of interoperability associated with the harmonization of data models.
|
|
-
|
Reducing the degree of service coupling fosters interoperability by making individual services less dependent on others and therefore more open for invocation by different service consumers.
|
|
-
|
Abstracting details about the service limits all interoperation to the service contract, increasing the long-term consistency of interoperability by allowing underlying service logic to evolve more independently.
|
|
-
|
Designing services for reuse implies a high-level of required interoperability between the service and numerous potential service consumers.
|
|
-
|
By raising a service’s individual autonomy its behavior becomes more consistently predictable, increasing its reuse potential and thereby its attainable level of interoperability.
|
|
-
|
Through an emphasis on stateless design, the availability and scalability of services increase, allowing them to interoperate more frequently and reliably.
|
|
-
|
Service Discoverability simply allows services to be more easily located by those who want to potentially interoperate with them.
|
|
-
|
Finally, for services to be effectively composable they must be interoperable. The success of fulfilling composability requirements is often tied directly to the extent to which services are standardized and cross-service data exchange is optimized.
|
A fundamental goal of applying service-orientation is for interoperability to become a natural by-product, ideally to the extent that a level of intrinsic interoperability is established as a common and expected service design characteristic.
