My blog has moved and can now be found at

No action is needed on your part if you are already subscribed to this blog via e-mail or its syndication feed.

Saturday, October 28, 2006
« Upcoming presentation on SOA, Interopera... | Main | Performance Engineering in a SOA »

I wanted to thank everyone who showed up for my presentation last Thursday. I was pleasantly surprised to see Yasser Shohoud who used to be a local and wrote one of the first and best books on web services back in the day. Given that he is a pretty smart guy, he got snapped up by Microsoft to work on the Indigo/WCF product team and then eventually moved out to work as a Technology Architect at the Microsoft Technology Center in Austin, Texas. Good to see you again, Yasser!

I had a great time and really enjoyed the interaction during and after the presentation. It was interesting for me to give a presentation that was stressing an architecture/business focused, standards based, vendor-neutral approach to SOA to an audience that was composed of MS technology developers and architects as well as Microsoft employees at a Microsoft Technology Center facility! The credit for establishing a forum that allows such diverse views definitely goes to Geoff Snowman, a local MS Technology Architect who is very involved in this space.

We actually had a pretty healthy discussion about the the role of ESBs in a SOA Environment. I recently came across this "ESB Market Report" that seems relevant to that conversation, so I thought I'd point to it. I resonate most closely with the comments made by Anne Thomas Manes in that article:

ESBs are just one type of SOA intermediary; other types are Web services management products, XML gateways, pureplay mediators like SOA Software and Apache Synapse, and platforms, according to Anne Thomas Manes, vice president and research director at Midvale, Utah-based Burton Group Inc.. She believes ESBs are best suited for complex aggregation and transformation of data, legacy access and orchestration. "I don't typically recommend using an ESB for mediation, they're more in the platform category," she said. "I typically recommend an XML gateway or Web services management product. Both have stronger security mediation."

My one point of ambivalence with Anne's comments are with the usage of ESBs for orchestration functionality. Orchestration to me has always been something that happened from a single perspective. A service or an application orchestrates a series of actions. As such, orchestration is to me a technical implementation of a Task-Based Service and is not something that should be in the Infrastructure. I have not been convinced that Orchestration Engines in the "Cloud" are the right way to move out.

To the person who had questions about WS-Notification and WS-Eventing, let me point you to:

There are some politics being played in this (Surprise!).. Check out this entry from Joe McKendrick to see the details.

As to the gentleman who brought up the SOA == Web Services question, I would like to provide a couple of resources that demonstrate the application of SOA principles but do NOT use Web Services.

SOA is an Architectural Style, Web Services are a standards based middleware platform for building Services. One does not equal the other.

10/28/2006 3:05 PM Eastern Daylight Time  |  Comments [0]  |  Disclaimer  |  Permalink   
Comments are closed.