Free Newsletters

  
Real World SOA | David Linthicum » Are you Building a JBOWS or a True SOA?

January 07, 2007 | Comments: (0)

Are you Building a JBOWS or a True SOA?

I enjoyed Joe McKendrick's blog where he sited a current study by Saugatuck Technology research that points out that SOA is still evolving, and that it's going to take a few years before the true value of SOA is a reality for most enterprises. Indeed, Joe goes on to say that many of the so called SOA implementations today are JBOWS, or "Just a Bunch of Web Services." Let's see, where have we heard that before?

From the study:

"However, according to Saugatuck, upon further probing, 'it became clear that many are merely managing a collection of Web services, and have yet to make a strong commitment to SOA as a management discipline — as opposed to an integration technology.'"

Truth-be-told SOA is, as I've said many times here, a true systemic change in the way you approach enterprise architecture. That's where the value is, and not just Web service-enabling you systems, or purchasing and implementing products with the "SOA hype label" bound to them (can you say governance? Can you say ESB?). It's the implementation of several layers of concepts as well as technology, custom fit to your requirements, and carefully considered given that this will be your foundation of IT going forward. Nothing more, nothing less.

So, are you building a JBOWS, or a true SOA? Here are a few things to consider:

- Are the services a true representation of the core behaviors found in your key enterprise systems, as well as new services required to provide other critical behaviors?
- Have those services been abstracted for most foreseeable uses?
- Is your information/data managed in such a way that you're loosely coupled from the underlying physical schemas?
- Are the services combinable into composites, and are those composites well defined?
- Is there a plan for governance and security, managing the use the services?
- Are both the information and services abstract-able to an orchestration/process layer for configuration-oriented agility of most of the IT assets?

I think you'll find that must early implementations of, at least the label of SOA, are actually "JBOWS." Not to worry, JBOWS can be a good start towards a SOA. Just know, you're not there yet.

Posted by Dave Linthicum on January 7, 2007 05:52 AM


RATE THIS ARTICLE:





 

  •  
  • COMMENTS




Dave:
The JBOWS concept is a convenient way to label the baby steps companies are taking as they build services on the path towards SOA.
And your six questions seem very appropriate as strategic guideposts.
What's missing are the set of practical, while you are at it (WYAAI), infrastruture and IT management steps that each company should be taking to get them to SOA from JBOWS.
For example, what are 3-4 things you should start putting in place over the next year to help ensure your information/data are loosely coupled from their sources
Better understanding what to do WYAAI will accelerate successful transition

Posted by: Robert Eve at January 9, 2007 12:22 PM

Nice list of "things to consider".
May I question, perhaps better, ask what is meant by
"...- Are the services a true representation of the core behaviors found in your key enterprise systems, as well as new services required to provide other critical behaviors?..."?

If this implies that the "...representation of the core behaviors..." reflects what the end-users have been using and are happy with, then OK.
If not, then may I suggest the addition of an item in which the "business services" aspects are also considered? Otherwise, the list appears to be somewhat "IT heavy" rather than business and IT working together.

Posted by: John Apps at January 11, 2007 12:24 PM

>>May I question, perhaps better, ask what is meant by
"...- Are the services a true representation of the core behaviors found in your key enterprise systems, as well as new services required to provide other critical behaviors?..."?


It means exactly what it says. :-)

It means are the services a replication of the core functions of an enterprise application. For instance, add_a_customer, delete_a_customer, etc.. and are there services added to make up for the delta between what the applications are doing, and what you need them to do.


Posted by: David Linthicum at January 11, 2007 01:08 PM

Technology White Papers

 

InfoWorld Technology Marketplace

» Technology White Papers Library

Technology White Papers by Topic

Technology White Papers E-mail Alert

Receive instant email notification when resources on this topic become available.
 
» BUY A LINK NOW

Sponsored Technology Links