|
|
|
|
Service-orientation and Object-orientation (Part I)
|
Those of you familiar with object-oriented (OO) analysis and design will recognize a similarity between a number of the service-orientation principles and the more established principles of object-orientation. Indeed, service-orientation owes much of its existence to object-oriented concepts and theory. Below we provide a look at which common object-orientation principles are related to the service-orientation principles we�ve been discussing.
Service reusability
Much of OO is geared toward the creation of reusable classes. The OO principle of modularity standardized decomposition as a means of application design.
Related principles, such as abstraction and encapsulation, further support reuse by requiring a distinct separation of interface and implementation logic. Service reusability is therefore a continuation of this OO goal.
Service contract
The requirement for a service contract is very comparable to the use of interfaces when building object-oriented applications. Much like WSDL definitions, interfaces provide a means of abstracting the description of a class. And, much like the �WSDL first� approach encouraged within SOA, the �interface first� approach is also considered an OO best practice.
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.
|
|
|
|
|
