Home > Service-Orientation
in the Real World > The Need for Service-Orientation (Part II)
|
...continued from previous page
Reduced Amounts of Application-Specific Logic
Increasing the amount of solution logic not specific to any one application or business process decreases the amount of required application-specific logic. This blurs the lines between standalone application environments by reducing the overall quantity of standalone applications. (See the Service-Orientation and the Concept of "Application" page.)
Figure: Business Process A can be automated by either Application A or Service Composition A. The delivery of Application A can result in a body of solution logic that is all specific to and tailored for the business process. Service Composition A would be designed to automate the process with a combination of reusable services and 40% of additional logic specific to the business process.
Reduced Volume of Logic Overall
The overall quantity of solution logic is reduced because the same solution logic is shared and reused to automate multiple business processes, as shown in the following figure.
Figure: The quantity of solution logic shrinks as an enterprise transitions toward a standardized service inventory comprised of “normalized” services.
Inherent Interoperability
Common design characteristics consistently implemented result in solution logic that is naturally aligned. When this carries over to the standardization of service contracts and their underlying data models, a base level of automatic interoperability is achieved across services. (See the Service-Orientation and the Concept of "e;Integration"e; page.)
Figure: Services from different parts of a service inventory can be combined into new compositions. If these services are designed to be intrinsically interoperable, the effort to assemble them into new composition configurations is significantly reduced.
|
