Introduction
 About this Site
 About the Principles

Common Principles of Service-Orientation
 Service reusability
 Service contract
 Service loose coupling
 Service abstraction
 Service composability
 Service autonomy
 Service statelessness
 Service discoverability

How Service-Orientation Principles Inter-relate
 Service reusability
 Service contract
 Service loose coupling
 Service abstraction
 Service composability
 Service autonomy
 Service statelessness
 Service discoverability

Service-Orientation and Related Principles and Paradigms
 Separation of Concerns
 Object-Orientation (Part I)
 Object-Orientation (Part II)
 Object-Orientation (Part III)

More
 Advanced
   service-orientation

 Submit your opinions
 Training for SOA and
   Service-Orientation

 About the author
About this Site
There is no single governing standards body that defines the principles behind service-orientation. Instead, there are many opinions, originating from public IT organizations to vendors and consulting firms, about what constitutes service-orientation.

Service-orientation has been in a constant state of evolution, influenced by established design platforms, such as object-orientation, and primarily geared toward providing a distinct approach for realizing a separation of concerns.

I spent a good amount of time researching service-orientation in preparation for solution designs and while writing my second book about SOA. I found it interesting how the IT industry, as a whole, is moving toward a service-oriented architectural model without a clear, universal definition of what service-orientation actually is.

Despite this disparity, there is a sufficient (and growing) amount of commonality. Part of my research resulted in what I�ve called the �Common Principles of Service-Orientation,� which collectively represent a cross-section of mainstream principles that characterize service-oriented design.

When building solutions around the use of the Web services technology set, applying service-orientation is what distinguishes the solution as being �service-oriented,� as opposed to a traditional distributed solution that happens to use Web services.

I therefore believe that it is very important to understand service-orientation (and how it differs from past design approaches) before embarking on establishing service-oriented architecture within your organization.

You�ll notice that the focus of this site is on service-orientation only, not on SOA itself. This Web site simply separates the fundamental service-orientation principles as they apply to individual services. It describes each principle, discusses how principles support and affect each other, and takes a look at how individual principles relate to object-orientation.

The content on this Web site consists of a series of excerpts from "Service-Oriented Architecture: Concepts, Technology, and Design", supplemented by quotes from various IT professionals.

Opinions

"When folks wrote screen-based transactions many months ago, they wrote it at a business function viewpoint: I add a customer, I add an order for that customer, I check backlogs for that customer, etc.

So in many respects, those CICS screens of 15 years ago are better suited to service orientation than a lot of the newer, distributed code that�s been written over the last several years, because of their affinity with a business function..."


- Phil Murphy, Forrester Research






www.soasystems.com

Copyright © 2005-2007 SOA Systems Inc.