This glossary supports the following titles:
SOA: Principles of Service Design (ISBN: 01323 44823, Prentice Hall)
Service-Oriented Architecture: Concepts, Technology, and Design (ISBN: 0131858580, Prentice Hall)
Service-Oriented Architecture: A Field Guide to Integrating XML & Web Services (ISBN: 0131 428985, Prentice Hall)
For more information about this book series, visit: www.soabooks.com
|
|
|
contract-to-implementation coupling
|
When details about a service’s underlying implementation are embedded within a service contract, an extent of contract-to-implementation coupling is formed.
This negative coupling type commonly results when service contracts are a native part of the service implementation (as with component APIs) or when they are auto-generated and derived from implementation resources, such as legacy APIs, components, and databases.
Implementation details within a service contract result in the requirement that service consumer programs physically bind themselves to these implementation characteristics, thereby causing dependencies that will be impacted whenever the implementation changes.
The “contract first” approach dictated by modern service-oriented design processes aims to avoid contract-to-implementation coupling by ensuring the service contract is designed independently of its eventual implementation environment.
See also:
- contract-to-functional coupling
- contract-to-logic coupling
- contract-to-technology coupling
- logic-to-contract coupling
- Service Loose Coupling
- service-oriented design
|
|
