[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

When Is Something Really SOA?

  • To: <xml-dev@l...>
  • Subject: When Is Something Really SOA?
  • From: "Chiusano Joseph" <chiusano_joseph@b...>
  • Date: Thu, 5 May 2005 16:25:03 -0400
  • Thread-index: AcVRsIUBxAvYEMSHR0q1e8XXpZPlVw==
  • Thread-topic: When Is Something Really SOA?

soa scenario
Here is a question has been on my mind for quite some time - I have some strong viewpoints on it, but would like to hear other viewpoints.
 
The general question is: When is something really a service-oriented architecture (SOA)?
 
By this I do not mean "what is an SOA", "what characteristics does an SOA have", etc. Rather, there seems to be a range of points on a continuum (call it the "service continuum", perhaps) at which someone may declare that they have implemented a service-oriented architecture.
 
In the past, I have pondered the following more specific question (please note that this is all scoped to Web Services-based SOA for ease of explanation):
 
If I have 2 Web Services that communicate, do I have an SOA? 
 
We can say "certainly not!". One can do point-to-point integration with Web Services just as easily (to a certain degree) as without, with redundant Web Services rather than shared Web Services (a violation of one of the foundational tenets of SOA, which is shared services).
 
Now let's add some more characteristics:
 
- The 2 Web Services share another Web Service in common for their processing (i.e. we now have a "shared services" scenario)
- The service provider one or more policies for a service consumer that interacts with it (these policies may address security, QoS, etc.)
- There is an electronic contract for interaction with the service provider (e.g. WSDL)
 
Add to this the fact that many (correctly, IMO) consider SOA to be a form of Enterprise Architecture, which (at least in my mind) implies enterprise-level benefits.
 
So the more specific question is:
 
Given the second scenario above (with the various added characteristics) and the fact that many consider SOA to be a form of EA ---
 
Is this second scenario large-scale enough that it *really* may be considered SOA? IOW, how large-scale does such an implementation need to be to *truly* be considered service-oriented architecture? When does one arrive at that point?
 
Joe
 

Joseph Chiusano

Booz Allen Hamilton

Visit us online@ http://www.boozallen.com


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.