Thursday, June 26, 2008

Enterprise Service Bus (ESB) Performance Revealed

It was recently that WSO2 released the 1.7 version of its Enterprise Service Bus (ESB). This release is based on Apache Synapse 1.2 which in turn is built on Apache Axis2 1.4.

There are many things that come in to play when deciding on which ESB to go with. Some of them are Performance, Licensing, Usability, Stability... etc. WSO2 has always been at the forefront when it comes to benchmarking ESB performance. You can find previous performance comparisons here and here. We've always been open as to how we conduct them and has always tried to get help from the relevant projects on how to configure them best.

Asankha the product manager of the WSO2 Enterprise Service Bus (ESB) recently published performance results based on its 1.7 release. The WSO2 Enterprise Service Bus (ESB) was compared with other leading implementations - both open source and proprietary. This comparison was done against a leading proprietary ESB, the proprietary version of an Open Source ESB, Apache Service Mix 3.2.1 and Mule Community Edition 2.0.1 (Mule CE). We cannot disclose the names of these proprietary ESB's cause they have a clause in there License saying that "Thou shalt not publish any performance results against us".

The results were pretty impressive. The WSO2 ESB outperformed all open source alternatives and it also outperformed the proprietary version of an Open Source ESB. Now what does that mean? The WSO2 ESB is the fastest open source ESB around (And thats with no specific performance tuning, Expect better results in the time to come.). The WSO2 Enterprise Service Bus (ESB) also displayed excellent stability on all scenarios.

Another interesting observation is that 1% of all requests sent to Mule CE 2.0.1 failing. Now who would want to use such a product in a production environment?

1 comment:

Martin Večeřa said...

"The WSO2 ESB outperformed all open source alternatives" - really? Their software engineers were not able to configure test services on the JBoss ESB that is well documented. How come?