|
|
|
|
Service autonomy and other principles
|
 Service autonomy and its relationship with
other service-orientation principles.
This principle applies to a service�s underlying logic. By providing an execution environment over which a service has complete control, service autonomy relates to several other principles, as follows:
|
Service reusability is more easily achieved when the service offering reusable logic has self-governance over its own logic. SLA-type requirements that come to the forefront for utility services with multiple requestors, such as availability and scalability, are more easily fulfilled by an autonomous service.
|
|
|
Service composability is also supported by service autonomy, for much of the same reasons autonomy supports service reusability. A service composition consisting of autonomous services is much more robust and collectively independent.
|
|
|
Service statelessness is best implemented by a service that can execute independently. Autonomy indirectly supports service statelessness. (However, it is very easy to create a stateful service that is also fully autonomous.)
|
|
|
Service autonomy is a quality that is realized by leveraging the loosely coupled relationship between services. Therefore service loose coupling is a primary enabler of this principle.
|
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.
|
|
|
|
|
