This glossary supports the following titles:
SOA Design Patterns
Web Service Contract Design & Versioning for SOA
SOA Principles of Service Design
Service-Oriented Architecture: Concepts, Technology, and Design
Modern SOA Infrastructure: Technology, Design, and Governance
SOA with REST
Next Generation SOA: A Real-World Guide to Modern Service-Oriented Computing
SOA with .NET & Azure
SOA with Java
SOA Governance
SOA Security: Practices, Patterns, and Technologies for Securing Services
SOA and Cloud Computing: Practices, Patterns, Technologies
This glossary also supports the SOA Certified Professional (SOACP) program.
For more information, visit: www.soacp.com
and
www.soaschool.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
|
|
