|
|
|
|
Service statelessness and other principles
|
 Service statelessness and its relationship with other service-orientation principles.
To successfully design services not to manage state requires the availability of resources surrounding the service to which state management responsibilities can be delegated. However, the principle of statelessness is also indirectly supported by the following service-orientation principles:
|
Service autonomy provides the ability for a service to control its own execution environment. By removing or reducing dependencies it becomes easier to build statelessness into services, primarily because the service logic can be fully customized to defer state management outside of the service logic boundary.
|
|
|
Service loose coupling and the overall concept of loose coupling establishes a communication paradigm that is fully realized through messaging. This, in turn, supports service statelessness, as state information can be carried and persisted by the messages that pass through the services.
|
Service statelessness further supports the following principles:
|
|
Service composability benefits from stateless composition members, as it reduces dependencies on individual services and minimizes the overhead of the composition as a whole.
|
|
|
Service reuse becomes more of a reality for stateless services, as availability of the service to multiple requestors is increased, and the absence of activity-specific logic promotes a generic service design.
|
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.
|
|
|
|
|
