Bitium vs. WSO2 Enterprise Service Bus

Best suited for companies that use the same services across multiple teams, services that might require support at one point. For us, it is very easy to share access to either the IT support team or to me, as the Salesforce administrator, and we can easily take care of the issue and then log out without any hassle.

I would not strongly recommend it for single users, who don't need to share access to others.

Incentivized

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

Incentivized

• Sharing access. It's as easy as 1-2-3 with Bitium, no more hassle with sharing the actual password and then changing it, violating company policies, etc.
• Lots of apps supported. In all three years since we are using Bitium, we haven't encountered any app that would not be supported by it.
• Easy to set up strong passwords. Another very easy and intuitive feature: when you are setting up an app, you can ask Bitium to generate an A-level password automatically, that you can therefore use with ease.

Incentivized

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

• Apps crashing. From time to time, some apps stop working in Bitium and they come back only after a while (1, 2, 8 hrs). We don't have a clear explanation for this yet.
• Very tied to Chrome. Bitium is almost 'married' to Chrome, making it unusable in other browsers, which is sometimes problematic.
• Sometimes slow Chrome Add-on. From time to time, the add-on seems so unresponsive that it is easier to go to the web dashboard and log in from there in the app you were looking for.

Incentivized

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

Incentivized

Compared to competitors the overall experience has been fine

Incentivized

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.

Incentivized

The product is performing well and consuming few resources

Incentivized

Our experience with the WSO2 support has beent satisfactory

Incentivized

It's the only one truly open source and free.

Adding a server node is really straightforward, there are just few point in the configuration files.

Incentivized

• Everyone is now required to have A-level passwords, so the overall level of security has increased a lot.
• Having a secured way of sharing access to different apps, users are now very open to being helped more hands-on by the support teams, not fearing that their credentials might be exposed or later used.

Incentivized

• 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