|
|
|
|
Service loose coupling and other principles
|
 Service loose coupling and its relationship with
other service-orientation principles.
Loose coupling is a state that supports a level of independence between services (or between service providers and requestors). As you may have already noticed, independence or non-dependency is a fundamental aspect of services and SOA as a whole. Therefore, the principle of persisting loose coupling across services supports the following other service-orientation principles:
|
Service reusability is supported through loose coupling, because services are freed from tight dependencies on others. This increases their availability for reuse opportunities.
|
|
|
Service composability is fostered by the loose coupling of services, especially when services are dynamically composed.
|
|
|
Service statelessness is directly supported through the loosely coupled communications framework established by this principle.
|
|
|
Service autonomy is made possible through this principle, as it is the nature of loose coupling that minimizes cross-service dependencies.
|
Additionally, service loose coupling is directly implemented through the application of a related service-orientation principle:
|
|
Service contracts are what enable loose coupling between services, as the contract is the only piece of information required for services to interact.
|
This page contains excerpts from:
Service-Oriented Architecture:
Concepts, Technology, and Design
by Thomas Erl
(ISBN: 0131858580, Prentice Hall/PearsonPTR, Hardcover, 792 pages).
For more information, visit www.soabooks.com.
|
|
|
|
|
