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

IBM WebSphere Message Broker vs Mule ESB 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

IBM WebSphere Message Broker
Ranking in Enterprise Service Bus (ESB)
8th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
13
Ranking in other categories
Application Infrastructure (16th)
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
 

Mindshare comparison

As of May 2025, in the Enterprise Service Bus (ESB) category, the mindshare of IBM WebSphere Message Broker is 3.9%, down from 5.6% compared to the previous year. The mindshare of Mule ESB is 20.4%, down from 22.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB)
 

Featured Reviews

BrajendraKumar - PeerSpot reviewer
Offers large-sized business information processing with a time-saving setup and impressive stability
I primarily use two previews of the product for Dev and two for QA as part of the production process. Whatever tools our company is using, the cost of a license in IBM WebSphere Message Broker is about 80% of all these software or tools. The message routing capabilities satisfy workflow efficiency. The product supports message formats of XML, JSON, and SSID, which are around 24 KB to 50 KB in size. The solution supports communication protocols like STTP and TCP. Features like DataGraph need to be introduced in IBM WebSphere Message Broker. Some of the clients of our organization are using an outdated version of IBM WebSphere Message Broker for which the vendor doesn't provide direct support anymore. For the aforementioned version, our company professionals can solve the queries on their own without seeking support from IBM. During the installation of a prior version of IBM WebSphere Message Broker, sometimes I have to configure the failovers through the cluster, where issues arise, and I often seek help from the support team. The solution is being used by some medicine companies in our organization that receive sales orders from the EDR or JDE. I would not recommend the product to others as its becoming obsolete and they can rather choose a middleware solution from Amazon or Azure. But I would overall rate the product a nine out of ten.
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.

Quotes from Members

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

Pros

"The documentation, performance, stability and scalability of the tool are valuable."
"It has many interfaces and you can connect to any backend source that has another format, and convert it to the desired format."
"It's reliable for our day-to-day operations, ensuring fast and secure data integration across different systems."
"It is a scalable solution...The setup is easy."
"The solution has good integration."
"We only use the basic features, but the most valuable one for us is the Publish-subscribe pattern."
"The transactions and message queuing are the most valuable features of the solution."
"Message Broker is valuable because most of the applications are using MQ. Even in my current engagement, the few applications which I audit to onboard the bank are using MQ."
"Scalability and load balancing."
"I am impressed with the product's connectors and scalability."
"The solution has a good graphical interface."
"Most of our use cases are for Salesforce. So, the connectors for Salesforce have been really helpful. They've made development two times faster."
"The connectors help to connect with a variety of applications."
"The most valuable feature is that it's programmer-friendly, so it's very easy to develop APIs."
"The solution's drag-and-drop interface and data viewer helped us quite a lot."
"The API management capabilities are exemplary. You can apply security policies to most applications, monitor logs, and get analytical data on request reception, response generation time, associated APIs, endpoints, and inbound and outbound messages."
 

Cons

"The installation configuration is quite difficult."
"Technical support is very slow and needs to be improved."
"The images and size of the containers are too big and I think that they should be more lightweight."
"Today I probably wouldn't go for Message Broker because of the cost structure, support, and the whole ecosystem around IBM."
"As our business requirements evolve, we require more dynamic capabilities to adapt and scale our services accordingly."
"The solution can add container engines such as docker."
"I know that Message Broker was a very tightly copied product with another IBM product, that is, IBM MQ. I would like to have a little bit more decoupling from the IBM MQ because it should not be a prerequisite for IBM WebSphere Message Broker usage."
"Stability and pricing are areas with shortcomings that need 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."
"The stability could be improved."
"The price of Mule ESB could improve."
"The payment system needs improvement."
"From an improvement perspective, there should be fewer coding challenges for users in Mule ESB."
"It's not easy to troubleshoot and we still can't make it work."
"It needs more samples. Also, the dependency on Maven should be removed."
"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."
 

Pricing and Cost Advice

"This product is more expensive than competing products."
"The solution is expensive."
"The price is very high and it's the main reason that we are searching for alternatives."
"IBM products are generally more stable and have more features, but also come at a greater cost."
"The licensing cost of IBM WebSphere Message Broker needs to be reduced"
"I feel with IBM, when you want certain functions or features, you have to continuously purchase add-ons. There are always additional fees."
"The solution is expensive."
"IBM software can be costly, but having a contract has helped manage and potentially lower costs over time."
"The solution is expensive."
"This is expensive. In my next project, we had to go to other vendor."
"You will not get any support from Mule ESB's team for the tool's community edition...You can get support with the licensed version of Mule ESB."
"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 product is expensive, but it does offer value for money."
"Most of the challenges that I had with this solution were for smaller customers. There is not a good licensing model or pricing model. It is more expensive than other solutions, and that's the downside of MuleSoft. I had to be creative to be able to sell it to the business, but we did. This is something they have to work on because for large companies, it's affordable, but for small and medium businesses, it's very hard to sell."
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
Financial Services Firm
30%
Computer Software Company
11%
Manufacturing Company
8%
Government
7%
Computer Software Company
17%
Financial Services Firm
15%
Manufacturing Company
9%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is your experience regarding pricing and costs for IBM WebSphere Message Broker?
IBM software can be costly, but having a contract has helped manage and potentially lower costs over time.
What needs improvement with IBM WebSphere Message Broker?
There could be greater flexibility and agility in service creation for the product. As our business requirements evolve, we require more dynamic capabilities to adapt and scale our services accordi...
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.
 

Also Known As

WebSphere Message Broker
No data available
 

Overview

 

Sample Customers

WestJet, Blue Cross and Blue Shield of North Carolina, Sharp Corporation, Michelin Tire
Ube, PacificComp, University of Witwatersrand, Justice Systems, Camelot
Find out what your peers are saying about IBM WebSphere Message Broker vs. Mule ESB and other solutions. Updated: April 2025.
849,686 professionals have used our research since 2012.