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

JBoss ESB vs Mule ESB vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

Mindshare comparison

As of June 2025, in the Enterprise Service Bus (ESB) category, the mindshare of JBoss ESB is 3.1%, up from 2.0% compared to the previous year. The mindshare of Mule ESB is 20.1%, down from 22.3% compared to the previous year. The mindshare of webMethods.io is 11.0%, up from 9.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB)
 

Featured Reviews

RS
Easy to use with flexible pricing, but needs more flexibility surrounding integrations
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.
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.
MohanPrasad - PeerSpot reviewer
Smooth integration and enhanced deployment with high licensing cost
webMethods.io was used to integrate APIs through the webMethods.io platform, trigger database events, and connect backend APIs through a Java backend. It was used extensively for integration purposes in my organization Integration became smoother, troubleshooting was easier, and deployment and…

Quotes from Members

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

Pros

"The solution is very easy to use. I can download the trial version and just give it a go."
"It is one of the best integration tools in the market."
"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 solution offers multiple deployment options."
"The most powerful feature is DataWeave, which is a powerful language where data can be transformed from one form into another."
"The solution's drag-and-drop interface and data viewer helped us quite a lot."
"The most valuable feature of Mule ESB is data transformation, i.e. our interacting with different systems and orchestrating for our business needs."
"Mule ESB helps a lot with our microservice architecture that we're trying to build, and it is still our go-to technology when it comes to that, so it's very promising for us."
"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."
"One [of the most valuable features] is the webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."
"Currently, we're using this solution for the integration server which helps us to integrate with the mainframe."
"What I like best about webMethods Integration Server is its portfolio of connectors."
"WebMethods.io is a powerful tool, but it requires skilled people who can fully utilize its potential."
"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."
"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."
"It integrates well with various servers."
"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."
 

Cons

"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."
"Improvements could be made in performance."
"The solution's setup needs to be a bit more straightforward and its support needs to respond faster."
"The payment system needs improvement."
"The price of Mule ESB could improve."
"There are limitations with the subscription model that comes with the product."
"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."
"The Anypoint platform consumes a lot of memory, and it would be great for developers if it were more lightweight."
"It's not easy to troubleshoot and we still can't make it work."
"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."
"The product's stability is an area of concern where improvements are required."
"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."
"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."
"This solution could be improved by offering subscription based licensing."
"The licensing cost is high compared to other options."
"Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area."
"The price has room for improvement."
 

Pricing and Cost Advice

Information not available
"This product is cheaper than some offered by other vendors, although there is a problem because you have to pay for some third-party adapters."
"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."
"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 various features and components for this solution are no longer free."
"Mule ESB is an expensive solution."
"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."
"The solution is expensive."
"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."
"The vendor is flexible with respect to pricing."
"Its cost depends on the use cases."
"The pricing is a yearly license."
"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."
"This is an expensive product and we may replace it with something more reasonably priced."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
"The product is very expensive."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
858,327 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
24%
Comms Service Provider
9%
Government
9%
Computer Software Company
9%
Computer Software Company
16%
Financial Services Firm
15%
Manufacturing Company
9%
Government
6%
Computer Software Company
14%
Financial Services Firm
13%
Manufacturing Company
13%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
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 Mu...
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 t...
What do you like most about Mule ESB?
The solution's drag-and-drop interface and data viewer helped us quite a lot.
What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage d...
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
 

Also Known As

No data available
No data available
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Rancore, Sprint, ResMed, Brazil's Ministry of Health, ING Services Polska
Ube, PacificComp, University of Witwatersrand, Justice Systems, Camelot
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about IBM, Salesforce, Oracle and others in Enterprise Service Bus (ESB). Updated: May 2025.
858,327 professionals have used our research since 2012.