JBoss SOA Platform vs. WSO2 Enterprise Service Bus

JBoss Enterprise SOA Platform is great when you are looking at building more or less pure Java applications and SOA micro-services that may integrate with multiple external data sources. It is less useful when you are looking to build simple SOA applications that are simple in nature since the overhead associated with deploying as well as learning BPEL.

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

• JBoss is open source so the cost overhead to deploy and build application is very low.
• JBoss Enterprise SOA Platform and its parent Redhat are reputed and well adapted in the industry so it is easy to find best practices documentation for complex deployments of JBoss middleware.

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.

• JBoss Enterprise SOA Platform is dependent and build for JEE/Java application so using a different programming paradigm will be much harder.
• There is still a learning curve to get familiar with BPEL making it harder to get an SOA micro-service up and running compared to a fully cloud-based service

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

Redhat support generally is great and that is true for the JBoss Enterprise SOA Platform as well. Even if you do not buy support from Redhat, you can reply on the discussion board and bug fixes via the open-source JBoss without much trouble.

Incentivized

Our experience with the WSO2 support has beent satisfactory

Incentivized

Oracle SOA Suite (Oracle BPM + Oracle BPEL + other components) and IBM WebSphere middleware is most costly and suited if you are already using applications and other middleware components from these vendors. Mulesoft (Salesforce Mule ESB) is best when you need deep integration with one of Salesforce's existing products. JBoss and Apache Web Server are best when you do not want to invest infant CapEx/OpEx on license fee. Apache Web Server based middleware is best for simple SOA applications.

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

• Positive impact on the business by being able to use existing Java/JEE expertise to build and deploy applications and business services.
• Positive ROI due to no license cost for JBoss Enterprise SOA.

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