Thursday, 11 September 2008

Mud Slinging and the Enterprise Service Bus

The last few weeks I've been reading up on the Enterprise Service Bus (ESB). I can tell you: it was an amazing journey. I started out with the book by David Chappell and from then on went to IBM DeveloperWorks which is usually a good spot to get technical info. These two sources combined give a nice overview of what an ESB could offer you, and how to put it to use.

That was not enough. I needed more information, especially on what an ESB really is and how to fit it into our architecture. So I looked at a couple of Blogs around the ESB and the Mediation patterns. What surprised me was the number of discussions and especially the tone of them. It seems the whole ESB discussion has degraded to a kind of mudslinging between different fundamental groups. One group states that the ESB is an architectural monstrosity which is not needed whenever the initial design of the service constructs adhere to standards of good design. The other group argues that there will never be such an environment. Oh btw, both groups think they hold the truth, the whole truth and nothing but the truth. Well, what else is new?

I think I understand where this argument is coming from. Just have a look at the ESBs that vendors today deliver. Probably the only thing they have in common is the name and the fact that it can do some routing and transformation. There the resemblance ends. In short, there's no clear definition of what an ESB is or does.

If I look at the architectural concepts that I found during my search, especially mediation, integration and security, there's a lot to be said about using these patterns. If you can find a tool (whether or not it is called an ESB) that fits your needs now and in the near future, why not use it?

So in my opinion, there's definitely a case to be made about an 'ESB'. Just don't know yet exactly what should be in there and what not .....

2 comments:

  1. The ESB was more of a markitecture 5 years ago..when the ESB book was written.

    JBI (JSR208) was the first attempt to standardize the ESB concept. Due to the vast # of promises (multi-platform, multi-languages, multi-protocol etc..pretty much everything under the middleware & integration sun) it couldn't fully become a standard. Now that many of the missing promises are fulfilled in the SCA you now have a practical ESB specification ready for implementation.

    Its strange that people researching ESB stop at it and do not look at JBI and SCA as extensions to it.

    ReplyDelete
  2. WSO2 Enterprise Service Bus

    We’ve taken a fresh look at old-style, centralized ESB architectures, and designed our unique WSO2 Enterprise Service Bus from the ground up as the highest performance, lowest footprint, and most interoperable SOA and integration middleware today. Relying on our innovative Carbon technology, the ESB delivers a smooth start-to-finish project experience that you cannot find anywhere else.

    ReplyDelete