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

IBM DataPower Gateway vs JBoss ESB comparison

Why PeerSpot?
 

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)
8th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Application Infrastructure (13th), SOA Application Gateways (1st), API Management (16th)
JBoss ESB
Ranking in Enterprise Service Bus (ESB)
7th
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 November 2026, in the Enterprise Service Bus (ESB) category, the mindshare of IBM DataPower Gateway is 4.9%, down from 6.4% compared to the previous year. The mindshare of JBoss ESB is 3.5%, up from 3.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Mindshare Distribution
ProductMindshare (%)
JBoss ESB3.5%
IBM DataPower Gateway4.9%
Other91.6%
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

"It is a scalable solution."
"The most valuable features of this solution are the appliance hardware, the software embedded within the hardware appliance machine, making it one of the best security platforms in the market that is easy to use, easy to install, and resilient for high availability."
"The advantages of IBM DataPower Gateway, which I personally appreciate, are the security features that you can manipulate according to your company policies."
"The solution's technical support is excellent."
"I recommend this solution; it is a good security application and it incorporates integrations and the latest security controls that are available in the market."
"It is easy to use, easy to install, and it's resilient for high availability."
"Since it is a gateway, it provides a lot of security features."
"The appliance has great security and reliability."
"The solution is very easy to use. I can download the trial version and just give it a go."
 

Cons

"The customization of the solution isn't as straightforward as we would like it to be."
"The programming language is only supported in XSLT and Gateway script."
"The components that they include in the product that are, in fact, a WTX, really need to be removed from the product because they tend to fail."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"It is a costly product."
"I noticed that the Gateway Script libraries could be improved, as they are not covering everything I need."
"The DCDR process should be less complex."
"New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS."
"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

"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"The tool's initial costing is expensive for small banks and financial institutions."
"IBM DataPower Gateway is quite expensive to get resources to work on this product. If the price could be cheaper, I think that will make it a little bit better and easily accessible to smaller clients. Then it could compete with other solutions that are available in the market. There's a whole lot of other solutions available that work well and are cheaper than IBM's products."
"It is an expensive solution."
"The licensing cost is very expensive."
"The solution has a return on investment but is a little expensive."
"The cost is very high and requires all five components in the API management solution."
"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.
922,528 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Outsourcing Company
9%
Manufacturing Company
8%
Healthcare Company
6%
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 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 is your primary use case for IBM DataPower Gateway?
The primary purposes for which IBM DataPower Gateway is used include security purposes, and sometimes you need to put some configurations and mapping into the process.
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: November 2026.
922,528 professionals have used our research since 2012.