TrustRadius: an HG Insights company

WSO2 Enterprise Service Bus

Score7.1 out of 10

13 Reviews and Ratings

What is WSO2 Enterprise Service Bus?

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.

Categories & Use Cases

My WSO2 ESB review

Pros

  • WSO2 ESB has a very nice Graphical UI for managing deployment of services and monitoring services. It uses Apache Synapse to manage the message mediation and can make changes within the UI at runtime and deploy it on-demand if necessary. It is open source and free.
  • WSO2 has an array of other enterprise level products that integrate with each other very well. WSO2 GREG for governance of service artifacts, WSO2 AM for identity management and their API manager.

Cons

  • WSO2 ESB has a lot of nice GUI elements and some for monitoring services. I think it could do away with them. The documentation and tutorials can be more updated with their product version.
  • I think support could be lot better in terms of their response times.

Return on Investment

  • I think it is a great product. We used it extensively for many years and I believe it has done it's job for us.

Alternatives Considered

Mule ESB

Other Software Used

Mule ESB

A light Insight in WSO2 ESB

Pros

  • 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.

Cons

  • WSO2 ESB needs to provide a GUI mapper tool like Tibco etc. When we are writing XSLT by ourselves, we are always more prone to error. So if there is a good mapper tool with a interactive user interface, it will expand the WSO2 market a lot.
  • Rest APIs concepts need to be more clarified and made in a simpler way. When using patterns with resources , there is a lot of confusion between URL mappings and URI templates. The documentation needs to be more extensive.
  • In Fault handling scenarios, right now WSO2 only provides unique error codes related to endpoint error handling but there should be a unique error code for other scenarios like transformation errors and validation errors.

Return on Investment

  • To be able to provide integrated solutions at sort notice.
  • Reduce the development cost as it is very user friendly and easy to learn.
  • Made management and monitoring of the projects more cost effective.

WSO2 ESB is THE CHOICE

Pros

  • Extensive EIP support.
  • Performance: very high throughput and low latency.
  • Security standards coverage.
  • Extensibility: if a mediator doesn't fit your needs you can extend it or even rewrite it.
  • Truly multi-tenant. No need to deploy separate instances to handle internal and external traffic.
  • First class production support.
  • Absolutely free. No enterprise paid add-ons. What you download (binaries and source code) is what it is.
  • WSO2 platform is growing fast with innovative products. Take a look at BAM roadmap as an example.

Cons

  • If you are used to heavyweight IDE with lots of wizards maybe you will miss it until you'll fall in love with fast and easy XML configuration.

Return on Investment

  • Take your spreadsheet and estimate TCO. SOA infrastructure like ESB is now commoditized and hard to go to commercial alternatives.

Why I am sticking to WSO2 ESB?

Pros

  • WSO2 ESB is really fast and reliable and it can be easily clustered.
  • As a developer it is easy to develop, maintain and trouble shoot with WSO2 ESB, its management console is really well designed.
  • Very good documentation and a real responsive community is supporting WSO2 and you can see the good changes, version by version.
  • It is free and open source and it [always] will be!

Cons

  • The management console is really good but sometimes when you haven't done an HTTP action (post/get) to the server and you are working with the sequences, you may lose some data after submission!
  • Sometimes error handling and built-in logging is not good, mostly when you are extending it with script mediators or class mediators.

Return on Investment

  • Very well documented tutorials and case studies makes it easy to learn.
  • It has a really supportive community
  • It is fast and it can easily handle 300 tps of average use on a VM with 4Gig RAM

wso2 esb for university services

Pros

  • It's really easy to install for a quick evaluation.
  • Open source. This is a must in our company.
  • It's highly scalable. Adding computing nodes is really straightforward.
  • Good product support, quick and effective.

Cons

  • While it's easy to configure for a quick start, it is not so easy to deploy by yourself in a complex production scenario.
  • Not very stable for production usage, we encountered several trivial bugs that make us believe that this product is still not widely adopted.
  • Lack of a built in mechanism for auto-restart in case of an application server crash.

Return on Investment

  • For developers it gave us the ability to wrap legacy services with little effort.
  • From an architectural/ sysadm point of view WSO2 application server is very different to manage than the other java application server we were using in our company, so the initial effort has been huge.

Other Software Used

Apache Web Server, Apache Tomcat, Bonita BPM

Usability