|
|
|
|
Service-orientation and Separation of concerns
|
Service-orientation is said to have its roots in an established software engineering theory known as �separation of concerns.� This theory is based on the notion that it is beneficial to break down a large problem into a series of individual concerns. This allows the logic required to solve the problem to be decomposed into a collection of smaller, related pieces. Each of these pieces addresses a concern or a specific part of the problem.
This theory has been implemented in different ways with different development platforms. Object-oriented programming and component-based programming approaches, for example, achieve a separation of concerns through the use of objects, classes, and components.
Service-orientation can be viewed as a distinct manner in which to realize a separation of concerns. The principles of service-orientation provide a means of supporting this theory while achieving a foundation paradigm upon which many contemporary SOA characteristics can be built.
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.
|
|
|
|
|
