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

IBM DataPower Gateway vs IBM Integration Bus 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 DataPower Gateway
Ranking in Enterprise Service Bus (ESB)
5th
Average Rating
8.4
Reviews Sentiment
6.5
Number of Reviews
31
Ranking in other categories
Application Infrastructure (12th), SOA Application Gateways (1st), API Management (12th)
IBM Integration Bus
Ranking in Enterprise Service Bus (ESB)
1st
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
70
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the Enterprise Service Bus (ESB) category, the mindshare of IBM DataPower Gateway is 6.6%, up from 5.9% compared to the previous year. The mindshare of IBM Integration Bus 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) Market Share Distribution
ProductMarket Share (%)
IBM Integration Bus20.4%
IBM DataPower Gateway6.6%
Other73.0%
Enterprise Service Bus (ESB)
 

Featured Reviews

AkshaySawant - PeerSpot reviewer
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.
Ashraf Siddiqui - PeerSpot reviewer
Helpful for complex integrations because it has tools and functionality to integrate with other systems
Everything needs to be improved. As far as integration and the cloud are concerned, things are moving to the cloud side. When you use Kubernetes and similar technologies, IBM Integration Bus doesn't greatly facilitate these environments. Maybe I don't know enough about that, but I feel that when it comes to the DevOps environment, the tool needs to be deployed on production in a way that's just like pods. Cloud integration needs to be more facilitated with the DevOps environment. This IBM technology needs to adapt because in the recent world, in the real world, we see that everything is just a cloud pod. Whenever you need to scale anything, you just put some cloud and pod and improve it, make any server and deploy it. But in IBM Integration Bus, there is a problem because we can't do this as easily. In short, IBM needs to more emphasize or more integrate with the cloud environments as well, similar to DevOps. There are limitations in IBM Integration Bus when it comes to DevOps.

Quotes from Members

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

Pros

"I like that it is very stable, and we never experience any downtime."
"What I like most is the stability."
"We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes."
"The solution is straightforward and for large organizations, it functions well."
"The solution is robust."
"The API Connect gateway service and the SQL injection feature is good."
"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."
"Its initial setup was straightforward."
"It's easy to develop things, and it's easy to handle."
"Promotes the reuse of developed resources to more efficiently consume resources."
"IBM Integration Bus is a very strong tool."
"We use IBM Integration Bus for document conversions."
"The most valuable feature is the API integration."
"Having the solution come from IBM you know you are receiving a product of quality in components and in the services, it is very good."
"Seamlessly integrates your different applications."
"It makes the communication between multiple and heterogeneous applications so easy. We can bring together different messages and applications from different platforms and connect them through IBM Integration Bus."
 

Cons

"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"It is a costly product."
"For the workloads that are not too high, appliance is a little bit expensive."
"The DCDR process should be less complex."
"Small and medium-sized companies might look for cloud-hosted applications due to the cost."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"They should improve the solution's clustering features."
"I can't say that there is any improvement I’m looking for. I’m new and haven’t connected with all features. For all drawbacks that were in the old version, I think they have been solved. The scalability needs improvement."
"To scale virtically, is difficult."
"The price could be better. It would also be better if they simplified the code."
"Its documentation is currently lacking. We have different environments where we use our configuration services, but we are not able to find documentation about how to deploy the local code to the server and how to set it up on a server level. I would like more documents from IBM that explain which variables should be in your machine while building a project, and when you deploy the code into the server, what should be their values. There are some variable values. I could not find such documentation. While working on a project, I developed the code on a local machine, and while deploying the code to our test environment, I made a couple of mistakes. We had to change some values at the server level, but we couldn't find any documentation regarding this, which made the task difficult."
"Licensing is too high. It is quite expensive."
"IBM doesn't really have a very strong community surrounding the product. Most of its direct competitors are open source solutions, and those have an excellent and well-developed community around the tech to help users navigate the ins and outs of the product. IBM is lacking in this area."
"There are a couple of things I want improved, but I think they have already touched upon all those things in the most recent version. I'm not using the most recent version—I use a version older than the most recent—but I'm sure that if I looked into and explored it, I would see more support on the CI/CD and more support for unit testing automation. I've read that they released all these things in the new version of App Connect. Once I explore the new version of this tool, I'll probably have a better idea of suggested improvements."
"IBM does not support orchestration, which is how they designed it, and other BPM tools in the market support orchestration. If they merged the BPM capability into this product, then it would be a better solution."
 

Pricing and Cost Advice

"The licensing cost is very expensive."
"The total cost of IBM DataPower Gateway would depend on the configuration, but in my experience, it can amount to 60,000 Euros per box, even for the virtual version. Usually, customers need high availability and a non-production environment, so the total price for IBM DataPower Gateway can be quite a lot. It can be 200,000 Euros or a similar figure."
"It's expensive when you compare it with others."
"The cost is very high and requires all five components in the API management solution."
"The tool's initial costing is expensive for small banks and financial institutions."
"The solution has a return on investment but is a little expensive."
"It is an expensive solution."
"The product is expensive."
"The price of the IBM Integration Bus is expensive. If you compare the price to the cloud version you can purchase what you need but the on-premise version price is flat."
"IBM provides a quite complicated licensing model."
"IBM Integration Bus itself is prices fair but App-Connect is a bit expensive which we use in conjunction with it."
"Pricing is on par with its competition."
"The pricing of the solution is high."
"For small companies, First of all, there are a lot of free products that could be used for integration. It can use the cloud or new implementation in the past. But if the tool is IBM, the official box in your company, you can make your submission and also publish the cloud to the work file. But let’s say, if you are working with premises, then you have to buy a reasonable main full support and gain experience with your product."
"The pricing could be improved to make it more competitive."
"Support costs are high compared to the competition. Otherwise, the support is good."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
872,706 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Insurance Company
10%
Computer Software Company
8%
Manufacturing Company
7%
Financial Services Firm
21%
Computer Software Company
12%
Manufacturing Company
8%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise17
By reviewers
Company SizeCount
Small Business15
Midsize Enterprise17
Large Enterprise47
 

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?
This product is definitely expensive because if any issue occurs in the live environment or production environment, and our organization faces some issue with the IBM DataPower Gateway, then the IB...
What needs improvement with IBM DataPower Gateway?
I have significant experience with the IBM DataPower Gateway. As a security product, it is very good. However, from the development perspective, it has limitations because it only supports the XSLT...
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 IBM Integration Bus?
The message queue, like, message queue connectors. Then they have a built in connectors for most of the systems, like SAP, oracle database, and this Civil connector is there. Of course, we have thi...
 

Also Known As

WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower
IBM WebSphere ESB
 

Overview

 

Sample Customers

RBL Bank, Availity
Salesbox, €sterreichische Bundesbahnen (€BB), Road Buddy, Swiss Federal Railways, Electricity Supply Board, The Hartree Centre, ESB Networks
Find out what your peers are saying about IBM DataPower Gateway vs. IBM Integration Bus and other solutions. Updated: September 2025.
872,706 professionals have used our research since 2012.