No more typing reviews! Try our Samantha, our new voice AI agent.

IBM DataPower Gateway vs JBoss ESB 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:
 

Categories and Ranking

IBM DataPower Gateway
Ranking in Enterprise Service Bus (ESB)
4th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Application Infrastructure (7th), SOA Application Gateways (1st), API Management (10th)
JBoss ESB
Ranking in Enterprise Service Bus (ESB)
8th
Average Rating
8.6
Reviews Sentiment
5.2
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2026, in the Enterprise Service Bus (ESB) category, the mindshare of IBM DataPower Gateway is 5.1%, down from 6.0% compared to the previous year. The mindshare of JBoss ESB is 4.0%, up from 3.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway5.1%
JBoss ESB4.0%
Other90.9%
Enterprise Service Bus (ESB)
 

Featured Reviews

AkshaySawant - PeerSpot reviewer
Manager at CSB Bank Ltd
Security features excel but development limitations emerge
We are using the IBM DataPower Gateway for security purposes. As per the development perspective, there are some limitations with IBM DataPower Gateway because it only supports XML and XSLT language, but it does not support the Java language. This is the only limitation of the IBM DataPower Gateway. For the authentication and authorization purpose, we can use the IBM DataPower Gateway. It's a very good product. We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes. If we are handling the load for a particular server, then we can use the IBM DataPower Gateway. The IBM DataPower Gateway is mostly used for security purposes. If we have some APIs and we are using some security for those APIs, then we can use it. It can also be used as a load balancer. It's also used for certificate management, user management purposes, authentication, and authorization. For routing, the IBM DataPower Gateway has multiple URL-based routing and content-based routing capabilities. If we have multiple URLs, then we can use an XML script. Using the XSLT language, we can configure multiple URLs and implement URL-based routing. Content-based routing means if we have multiple requests, we can route the request to a particular URL. For this, we need to use the XSLT language only. We can't use XML, Java, or other scripting languages. With IBM DataPower Gateway, we are using all the APIs. All APIs have been configured on the gateway. We have configured the particular TLS profile and some TLS client profiles as well. Using that TLS profile, we have configured the APIs and authentication. We have configured some tokens also, including JWT tokens and different types of auth tokens. There is also a rate limiting feature which we use for handling API loads.
AU
Senior Software Engineer at Deloitte
Efficient orchestration and security features improve business processes effortlessly
JBoss ESB should focus on startup and performance as EAP is heavier than lightweight Java frameworks, which impacts microservices and cloud environments. Improvements should include faster start times and reduced memory footprints. Better cold-start performance in containers should be emphasized. Cloud-native features must be enhanced since many enterprises are shifting to Kubernetes and OpenShift, making EAP more cloud-friendly. This could include providing smaller container images, native auto-scaling support, and improved integration with cloud configuration services. Enhancing the developer experience is crucial; while the current configuration is powerful, it can be complex for newcomers. As an experienced user, I navigate it easily, but newcomers struggle due to heavy reliance on XML configuration. Transitioning to a JSON-based configuration or YAML format would be beneficial, and simplifications in clustering setup for local testing would greatly assist users.

Quotes from Members

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

Pros

"I like the API Gateway feature."
"We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes."
"I like the API Gateway feature."
"It is easy to use, easy to install, and it's resilient for high availability."
"The API Connect gateway service and the SQL injection feature is good."
"The product is stable...The product is scalable."
"Since it is a gateway, it provides a lot of security features."
"For me, its most valuable features include: the fact that it's high-speed, its ability to be remotely administered via an API, the fact that it can deal with multiple protocols, and it's very quick to make changes to the setup."
"The solution is very easy to use; I can download the trial version and just give it a go."
"The solution is very easy to use. I can download the trial version and just give it a go."
 

Cons

"The initial setup isn't so easy, you need who has experience working with the solution to help."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"The product should be more adapted to the DevOps process."
"We are always looking for more features wherein it could be easily integrated with cloud applications. We are looking for either a cloud solution or a cloud integration option."
"The programming language is only supported in XSLT and Gateway script."
"The DCDR process should be less complex."
"In the next release, I would like to see the product price reduced. It should be cheaper."
"DataPower isn't the most user-friendly tool. It is not an easy tool to use. Some things could use better wizards to guide you through processes."
"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."
"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."
"JBoss ESB should focus on startup and performance as EAP is heavier than lightweight Java frameworks, which impacts microservices and cloud environments."
 

Pricing and Cost Advice

"The cost of this product varies from customer to customer and the relationship with IBM, including how many offerings from IBM are already being used."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"As far as I know, they have a perpetual license for this product. They are paying perpetual fees rather than an annual subscription or annual pricing."
"The licensing cost is very expensive."
"The solution has a return on investment but is a little expensive."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"It's expensive when you compare it with others."
"The product is expensive."
Information not available
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
893,915 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Insurance Company
8%
Manufacturing Company
8%
Government
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise18
No data available
 

Questions from the Community

What do you like most about IBM DataPower Gateway?
The MPGW (Multi-Protocol Gateway) is great because it allows you to easily expose services using various protocols – web services, REST (JSON), and others. This flexibility simplifies things.
What is your experience regarding pricing and costs for IBM DataPower Gateway?
I don't know if the current licensing cost of IBM DataPower Gateway is high, but I think it's acceptable. I don't have any complaints about it.
What needs improvement with IBM DataPower Gateway?
I noticed that the Gateway Script libraries could be improved, as they are not covering everything I need.
What needs improvement with JBoss ESB?
JBoss ESB should focus on startup and performance as EAP is heavier than lightweight Java frameworks, which impacts microservices and cloud environments. Improvements should include faster start ti...
What advice do you have for others considering JBoss ESB?
I am currently using JBoss ESB as an end user. I chose JBoss ESB because it is excellent for open source Java, Java EE, and Jakarta applications. Initially developed by JBoss, it was later acquired...
What is your primary use case for JBoss ESB?
I used JBoss ESB for banking API and banking software. We created our own modules since banking APIs and banking applications require extensive security measures. Since banks handle sensitive finan...
 

Also Known As

WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower
No data available
 

Overview

 

Sample Customers

RBL Bank, Availity
Rancore, Sprint, ResMed, Brazil's Ministry of Health, ING Services Polska
Find out what your peers are saying about IBM DataPower Gateway vs. JBoss ESB and other solutions. Updated: April 2026.
893,915 professionals have used our research since 2012.