This glossary supports the following titles:
SOA Governance
SOA with .NET & Azure
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: Principles, Patterns & Constraints
Next Generation SOA: A Real-World Guide to Modern Service-Oriented Computing
SOA with Java
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-technology coupling
|
When the contract exposed by a service is bound to non-industry standard communications technology, it forms an extent of contract-to-technology coupling.
Although this coupling type could be applied to the dependencies associated with any proprietary technology, it is used exclusively for communications technology because that is what service contracts are generally concerned with.
An example of contract-to-technology coupling is when the service exists as a distributed component that requires the use of a proprietary RPC technology.
Contract-to-technology is a negative coupling type because by forming dependencies on proprietary communications technologies the service contract imposes these dependencies onto its consumer programs. Web services are most commonly used to avoid this coupling type.
See also:
- contract-to-functional coupling
- contract-to-logic coupling
- contract-to-implementation coupling
- logic-to-contract coupling
- RPC
- Service Loose Coupling
- Web service
|
|
Arcitura IT Certified Professionals (AITCP)
Arcitura IT Certified Professionals (AITCP)
Arcitura IT Certified Professionals (AITCP) 
Arcitura YouTube Channel
