We changed our name from IT Central Station: Here's why

JBoss ESB OverviewUNIXBusinessApplication

JBoss ESB is #14 ranked solution in top Enterprise Service Bus (ESB) tools. PeerSpot users give JBoss ESB an average rating of 8 out of 10. JBoss ESB is most commonly compared to Mule ESB: JBoss ESB vs Mule ESB. The top industry researching this solution are professionals from a computer software company, accounting for 28% of all views.
What is JBoss ESB?
JBossESB is the next generation of EAI - better and without the vendor-lockin characteristics of old. As such, many of the capabilities mirror those of existing EAI offerings: Business Process Monitoring, Integrated Development Environment, Human Workflow User Interface, Business Process Management, Connectors, Transaction Manager, Security, Application Container, Messaging Service, Metadata Repository, Naming and Directory Service, Distributed Computing Architecture. Plus JBossESB is part of an SOI (Service Oriented Infrastructure). However, SOA is not simply a technology or a product: it's a style of design, with many aspects (such as architectural, methodological and organisational) unrelated to the actual technology.
Buyer's Guide

Download the Enterprise Service Bus (ESB) Buyer's Guide including reviews and more. Updated: January 2022

JBoss ESB Customers
Rancore, Sprint, ResMed, Brazil's Ministry of Health, ING Services Polska
JBoss ESB Video

JBoss ESB Reviews

Filter by:
Filter Reviews
Filter Unavailable
Company Size
Filter Unavailable
Job Level
Filter Unavailable
Filter Unavailable
Filter Unavailable
Order by:
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Showingreviews based on the current filters. Reset all filters
Financial Technology Solution Consultant at Intellect Design Arena Ltd
Top 5
Easy to use with flexible pricing, but needs more flexibility surrounding integrations
Pros and Cons
  • "The solution is very easy to use. I can download the trial version and just give it a go."
  • "The EPA, from what I understand, lacks a lot of features and it doesn't really know how to interface with legacy systems or how to develop APIs for legacy systems."

What is most valuable?

The solution is very easy to use. I can download the trial version and just give it a go. 

The pricing is flexible. It has some other products that give me a lot of flexibility, like the OS from Red Hat. The middleware is there, and the web layer is there as well. It's a good combination of offerings, which we can really use to help position them to some other solutions.

What needs improvement?

The EPA, from what I understand, lacks a lot of features and it doesn't really know how to interface with legacy systems or how to develop APIs for legacy systems. 

I'm not sure if it is possible, however, we would like to see features that allow for legacy systems so that they can continue to be developed and managed well.

The solution should provide some more general studio features. We should be able to manipulate the platform in order to do some integrations on our own. There needs to be a bit more flexibility.

For how long have I used the solution?

We've been using the solution for about two years now. We've been testing it.

What do I think about the stability of the solution?

The solution is very stable. It's reliable. Users don't have to worry about bugs or glitches. There aren't really any crashes. It's been good for us so far.

What do I think about the scalability of the solution?

We've found the scalability to be good. If we need to expand the solution, we believe we would have not problems actually doing so.

Currently, we have about 700 people on the solution. They are all end users.

How are customer service and technical support?

Technical support has been good. It's a little bit expensive to have the option for technical support, however, largely we have been satisfied. They're responsive and they help us deal with any issues that arise.

Which solution did I use previously and why did I switch?

We tried some other solutions and experimented with trial versions. We've tried Mule, for example. We needed something that would work well with Red Hat, and we find that JBoss is very good in that sense.

How was the initial setup?

The solution is both straightforward and complex. It's a bit of a combination of both, to be honest.

Deployment takes a few days.

Largely, the implementation was handled by someone else. We ended up getting outside help to implement the solution fully, and we were quite satisfied with the results.

What about the implementation team?

We employed an individual to help us with the implementation. It was a partner or a reseller. I'm not sure exactly who it was. They did a good job though.

What was our ROI?


What's my experience with pricing, setup cost, and licensing?

You do need to pay for technical support, which is pricey.

Which other solutions did I evaluate?

We can't complain about the product. It's good. However, there are so many others that are up and coming. The market is getting saturated with options. There are a handful of other products - maybe two or three - that we would also recommend.

What other advice do I have?

We are simply a customer, and we use the solution within our organization. We don't have a special professional relationship with JBoss

I don't recall which version of the solution we are using. It's about a year and a half old at this point.

Overall, I'd rate the solution seven and a half out of ten.

Which deployment model are you using for this solution?

Disclosure: I am a real user, and this review is based on my own experience and opinions.