Try our new research platform with insights from 80,000+ expert users

Mule ESB vs OpenESB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 3, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Mule ESB
Ranking in Enterprise Service Bus (ESB)
2nd
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
49
Ranking in other categories
No ranking in other categories
OpenESB
Ranking in Enterprise Service Bus (ESB)
14th
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the Enterprise Service Bus (ESB) category, the mindshare of Mule ESB is 20.4%, down from 22.2% compared to the previous year. The mindshare of OpenESB is 1.5%, up from 1.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB)
 

Featured Reviews

PurbayanSaha - PeerSpot reviewer
Has API-led architecture and provides a unique, user-friendly, and scalable architecture for hosting APIs
There's room for improvement in multi-file transfer functionality. It's not convenient when using MuleSoft, and it should have better capability for handling large amounts of data. For example, applications like GoAnywhere can handle huge chunks of data, so the tool should also have something to facilitate that aspect of integration.
PP
Enables us to define the business process and integrate it with other software
I used to work with Integration Bus. What is interesting is that the two products were made mainly by the same team, but OpenESB is lighter, you can run it on a simple GBM. It's lighter and has quite a few resources, no application server, and no database. This provides you with more intelligence because there is some kind of friction in the routing service, and you can play with that friction to provide some connection policy, like the last deployed policy. For example, if you were to install version one, and afterward, you deployed version two, automatically — if you decided that your connection will be the right deployed connection — you would be routed to the last version. If it doesn't work, you would just need to redeploy version one. Also, there are higher-level concepts, such as the interface of services, which allows you to define your interface and choose the method of implementation, like Java for example. On the other hand, with OpenESB, I am more connected. At the monitoring level, you can trust the level and replay the process, which is interesting, but because you have to store everything on the database, you have a conventional system that makes your system require more resources. The push ability to extract data from the process and then publish it in the data container is very interesting. For example, by using a database like Google's big data analytic search, you can create your own analytics from the data in your process without disturbing the process.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It's open source, and there are a lot of community resources. Mule ESB makes it easy to connect to other software applications."
"I like that Mule ESB provides fast and good technical support."
"I like that it's user-friendly. Compared to other ESBs, I find it easier to use. I like it better than other ESBs. I like the connectors, which make calling the APIs through the routers easier."
"The product offers a community edition that is free of cost."
"Once it is started, we don't see any problems on a day to day basis."
"The most valuable features of Mule ESB are its ease of use, documentation, ease to adapt to newer security and vulnerabilities, and a lot of help available. Additionally, there is a lot of flexibility, many patches available, and they provide APIs. They are a market standard."
"This tool has exceptional API management and integration connectors in addition to multiple out of the box connectors."
"It is easily deployable and manageable. It has microservices-based architecture, which means that you can deploy the solution based on your needs, and you can manage the solution very easily."
"One of the most valuable features is being able to implement business processes while keeping track of the design from BPMN to a BPEL Implementation."
"The process-oriented solution allows you to define choreography and orchestration."
"The core is very stable."
"OpenESB pushes the organization to clearly define service boundaries and interfaces. So it motives the business and the development teams to clearly define their business services and processes they want to implement. OpenESB supports fine and coarse-grain granularity for the services and supports top-down and bottom-up approaches for the services, processes definition, and composition."
 

Cons

"In the next release, I would like to see improvement in the generator for the DataWeave language so that it's a little more graphic."
"One area that could be improved is the way that policies are propagated when APIs are moved from one environment to another. It's an issue, but when you develop and test the rest APIs in a lower environment and need to move them, there's a propagation process. This process moves certain aspects of the APIs, like the basic features. But when we move them, the policies don't always move with them. The policies should be able to move so we don't have to redo them manually. There are some APIs we use, but it's a bit tedious."
"Lacking some connectors that could be included."
"The payment system needs improvement."
"In order to meet the new trend of active metadata management, we need intelligent APIs that can retrieve new data designs and trigger actions over new findings without human intervention."
"I would like to see support for BPM in the next release of this solution."
"Mule ESB isn't as secure as IBM. Financial companies go with IBM for that reason."
"We would like the ability to use our own code. This would allow us to develop customizations with ease. Additionally, it would be nice to have more analytics or insights on the exchanged information between databases."
"Cloud deployment is weak and needs to be improved."
"The documentation needs to be better."
"Regarding its management, a web console being able to synchronize distributed instances would be great."
"The documentation of the product must be improved. It could be tricky to find the right documentation on a topic since the documentation is spread in many places. I advise the new joiner to contact the community to get entry points and additional documentation. Tutorial and Video must be present to take up the product."
 

Pricing and Cost Advice

"Mule ESB is an expensive solution."
"The licensing is yearly, and there are additional fees for services."
"Plan your licensing model (cloud or on-premises or hybrid) that will allow seamless integration with new partners."
"I think the price is very high. If you use TIBCO BW, the license is for the CPU usage, then the IPS, and support. I also think the license for the product is a one-time expense."
"This is expensive. In my next project, we had to go to other vendor."
"The solution is expensive."
"Regarding licensing and pricing, I find it somewhat flexible. They are more flexible with larger customers compared to small and medium ones, as their licensing model depends on ports and other factors. Large customers benefit from more flexibility in implementation and renewal compared to smaller ones."
"The various features and components for this solution are no longer free."
"The cost for the prediction instrument is high because it is charged per instances based on prediction, but the rest of the solution is free."
"The Community Edition is a full product you can use in production, it does not have limitations like other alternatives."
"There are two versions. The first is the community version, which is free and contains the last part of the feature, but if you want to get the Enterprise version, you'll have to pay €60,000 which covers support and two instances on production."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
849,686 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
15%
Manufacturing Company
9%
Government
6%
Computer Software Company
17%
Financial Services Firm
14%
Manufacturing Company
9%
Hospitality Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Migration from IBM Integration Bus to Mulesoft ESB for a large enterprise tech services company
I was previously part of the Oracle SOA/OSB development team. In my current capacity I architected solutions using MuleSoft Anypoint Platform on cloud / on-premises and hybrid modes and on PCE/RTF ...
IBM Integration Bus vs Mule ESB - which to choose?
Our team ran a comparison of IBM’s Integration Bus vs. Mule ESB in order to determine what sort of ESB software was the best fit for our organization. Ultimately we decided to choose IBM Integratio...
What do you like most about Mule ESB?
The solution's drag-and-drop interface and data viewer helped us quite a lot.
Ask a question
Earn 20 points
 

Comparisons

 

Overview

 

Sample Customers

Ube, PacificComp, University of Witwatersrand, Justice Systems, Camelot
Information Not Available
Find out what your peers are saying about Mule ESB vs. OpenESB and other solutions. Updated: April 2025.
849,686 professionals have used our research since 2012.