Home > SOA Glossary > Contract-to-Technology Coupling

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: