Comparing to earlier versions of WSO2 ESB, this version has improved significantly in mediation performance.
In this version, Pass-through HTTP transport is used as the default http transport.
Pass-through transport is there since ESB 4.0.0 but the major disadvantage in previous versions is, Pass-through transport was supported only for pass through mediation scenario (pass through proxy) and for the transport header based routing. Content aware mediation scenarios like CBR (content based routing) was not supported by Pass-through transport. That prevented making the Pass-through the default transport for HTTP even though it performs well over NHTTP transport.
In 4.6.0, Pass-through transport supports both content aware and content unaware mediation scenarios, so now there is nothing preventing from making it the default transport for http. Hiranya has written a very nice detailed post on “How the World's Fastest ESB was Made” explaining the history and the technology behind the Pass-through transport.
Recent performance evaluation, ESB Performance Round 6.5 shows how well the WSO2 ESB 4.6.0 outperforms the others. Following is a graph extracted from the results published in ESB Performance Round 6.5.
Following graph illustrate the memory usage throughout 40 hours of long running performance test.
It indicates how stable ESB 4.6.0 under high load for a long period of time.
Last week I got a chance to work on implementing an integration scenario for a tutorial session of WSO2Con 2013 together with Kasun and Ishan.
The scenario is an extended version of well known “How to GET a Cup of Coffee the WSO2 Way” integration scenario.
Following are some of the key parts of that scenario.
- Exposing a REST API for a SOAP service through ESB
- JSON Handling
- XSLT transformations
- User authentication through Oauth
- JMS Message Stores and Message Processors
- Content based routing
- Protocol switching
- Many other EIP patterns like Message cloning/Iteration/aggregation
- Integration with Data services
- Integration with Message brokers
- Sending Email notifications
- Sending Tweets
We managed to implement all above scenarios using ESB 4.6.0.
That indicates how well the default Pass-through Http transport behaves for both content aware and content unaware scenarios.
Some of the minor but very useful improvements done in 4.6.0 is yet hidden under the shadow of this huge performance improvement.
Callout mediator has improved significantly. Now Callout mediator supports following features.
- Can specify a security policy to invoke secured services
- Has an option to specify different security policies for inbound and outbound paths
- Can specify an Address Endpoint instead of the service url
- Support sending soap headers
- Support sending transport headers
These facts clearly indicates that WSO2 ESB 4.6.0 release is not just about performance.
