WSO2 says they have taken a fresh look at old-style,
centralized ESB architectures, and designed their unique WSO2 Enterprise Service Bus
from the ground up as the highest performance, lowest footprint, and most
interoperable service oriented architecture (SOA) and integration middleware
today. Additionally, the vendor says that by relying on their carbon technology
the ESB is able to deliver a smooth start-to-finish project experience.
I have recently been using Mule ESB. I also found their product to be solid. I like how you can develop message mediation rules in Mule Eclipse IDE. They have a lot of features to build services with less custom development.
WSO2 ESB's biggest advantage over them is that it is an open source project. It has no heavy licensing fees and expensive contract fees. WSO2 provides the same level of scalability and stability. WSO2 ESB is very light weight and developer friendly. The WSO2 ESB run time …
WSO2 ESB is an awesome product for companies looking to venture into the world of SOA with an ESB. They have a lot of other products too that can work really well with their carbon infrastructure. The interface is simple for deploying and managing proxy services. You can also write custom modules within the ESB using Java with IDE like Eclipse
One of the basic requirement of an ESB product is that it should be able to support transformation. WSO2 ESB provides support of XSLT, so you can transform your request to whatever format. Moreover, transformations like converting your xml payload into JSON and JSON payload to XML are out of the box available.
WSO2 ESB provides a scheduler feature, by which you can configure your own scheduler to call a proxy service at a particular time of day or or initiate sequence.
WSO2 ESB provides excellent error handling techniques, WSO2 ESB provides detailed error handling scenarios to tackle all the situations. WSO2 ESB also provides custom error handling by which you can make your own custom error message before sending it back to client.
Lack of auto-restart built-in capabilities. In case of running out of memory there are no built-in methods to recover from a crash, just for example, Oracle WebLogic Node Manager.