|
|
|
|
Services are composable
|
A service can represent any range of logic from various types of sources, including other services. The main reason to implement this principle is to ensure that services are designed so that they can participate as effective members of other service compositions, when required. This requirement is irrespective of whether the service itself acts as the composer of others.
A common SOA extension that underlines composability is the concept of orchestration. Here, a service-oriented process (which essentially can be classified as a service composition) is controlled by a parent process service that composes process participants.
 The UpdateEverything operation
encapsulating a service composition.
The requirement for any service to be composable also places an emphasis on the design of service operations. Composability is simply another form of reuse and therefore operations need to be designed in a standardized manner and with an appropriate level of granularity in order to maximize composability opportunities.
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.
|
|
|
|
|
