[5] The agility promised by a service-oriented architecture (SOA) is usually measured in terms of the reusability level of its contained services.
This clearly adds overhead, and stands in the way of service interoperability and reuse.
Schema centralization directly supports the objectives of data model standardization[10] design pattern, which further supports creation of centrally governed schemas.
Secondly, to apply this design principle effectively, the actual contract must be physically isolated from the service logic and implementation so that it can be based on industry standards.
This can be achieved by the application of a decoupled contract[11] design pattern.
Also that the ‘contract first’ approach needs to be followed so that the underlying logic only makes use of standardized data models.