Free Newsletters

   All InfoWorld Newsletters
Real World SOA | David Linthicum » Reflecting on SOA in 2006

December 20, 2006 | Comments: (0)

Reflecting on SOA in 2006

So, was 2006 the year of the SOA? Hardly. I think it was the year of talking about SOA, and perhaps dong some minor SOA projects. I think 2007 will be more of the same, but with an increasing amount of implementation work done towards the end of the year. Mark my words. Okay, I think I'm marking my own words.

Some of the positive things when considering SOA in 2006:

SOA has increased awareness of the underlying architectures within enterprises, and how they may or may not limit business. In essence we're shinning a light on bad architecture when dealing with the notion of SOA.

SOA has driven a new set of startup companies, with some pretty good ideas. These include governance, process management, and security, as applied to SOA.

I attended better and more informative SOA conferences this year. We seem to be getting beyond the hype, into the meat of the topic, and understand better the work that needs to be done.

Some of the negative or silly things, when considering SOA in 2006:

"SOA 2.0" The last time I'll say that one.

Most of those implementing SOA don't really get the concept yet, as I'm finding. Needed is more education and mentoring.

Perhaps too much consolidation in this space, and too soon. Most of those SOA fledgling companies never got to spread their wings.

The hype was too high. One needed to scream to get above the noise in 2006. Unfortunately, I think it's going to get worse before it gets better.


Posted by Dave Linthicum on December 20, 2006 04:57 AM


RATE THIS ARTICLE:





 

  •  
  • COMMENTS




In 2006 many people thought of SOA as synchronous RPC (mostly over Web Services). Others said EDA is SOA. And there were many people who said that the best of EDA and SOA is combined in SOA 2.0.

Everybody will agree that there is a request-and-reply pattern and a publish-and-subscribe pattern. It is easy to see that both patterns are an inverse of each other. In my article "How EDA extends SOA and why it is important" I explained the differences between the two patterns and when to use the one or the other (http://soa-eda.blogspot.com/2006/11/how-eda-extends-soa-and-why-it-is.html).

Because of the completely different nature and use of the two patterns, it is necessary to be able to distinguish between the both and to name them (which we didn't in 2006). You might say making such a distinction is a universal architectural principle. Combining both of the patterns into an increment of the version number of one of them was not a very clever act. I believe it is appropriate and desirable to use the acronyms SOA and EDA to make this distinction, because SOA and EDA are both positioned in the same architectural domain; SOA focusing on (the decomposition of) business functions and EDA focusing on business events. Let us hope 2007 will deliver better insight to the community.

To read more: http://soa-eda.blogspot.com

Posted by: Jack van Hoof at December 21, 2006 01:27 AM

Technology White Papers

 

InfoWorld Technology Marketplace

» Technology White Papers Library

Technology White Papers by Topic

Technology White Papers E-mail Alert

Find out when the latest white paper is available:
 
 
» BUY A LINK NOW

Sponsored Technology Links