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

IBM DataPower Gateway vs IBM WebSphere Message Broker 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)
4th
Ranking in Application Infrastructure
7th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
SOA Application Gateways (1st), API Management (10th)
IBM WebSphere Message Broker
Ranking in Enterprise Service Bus (ESB)
9th
Ranking in Application Infrastructure
16th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
13
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 IBM WebSphere Message Broker is 5.0%, up from 3.9% 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%
IBM WebSphere Message Broker5.0%
Other89.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.
BrajendraKumar - PeerSpot reviewer
Technical Architect at HCL Technologies
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.

Quotes from Members

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

Pros

"DataPower Gateway is a perfect product, and I would recommend using it because it provides a lot of benefits."
"Support for PCA and non-PCA services is valuable."
"The solution is very easy to work with."
"From a technical point of view, IBM DataPower Gateway performs quite well, so my team had no concerns at all in terms of performance, reliability, and stability."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"It's high-speed and it can be remotely administered via an API."
"The scalability of the solution is good."
"Since it is a gateway, it provides a lot of security features."
"We have a large number of use cases for this product, and it is built into the underlying infrastructure for most of our applications."
"Straightforward development and deployment."
"Before the cloud, it was very easy for us to build and it was quick to integrate."
"The most valuable feature of IBM WebSphere Message Broker is the ability to facilitate communication with legacy systems, offering a multitude of great capabilities. For example, if there is a mainframe system in place with a web service serving as the front end. In that case, the solution enables efficient protocol transformations to convert all request payloads into a format that the legacy systems can accept, rendering the integration and transformation processes seamless and highly effective."
"It's reliable for our day-to-day operations, ensuring fast and secure data integration across different systems."
"We only use the basic features, but the most valuable one for us is the Publish-subscribe pattern."
"This is a very reliable and stable solution that is used for a very large number of transactions."
"It is a scalable solution...The setup is easy."
 

Cons

"IBM DataPower Gateway is a great solution but when based on utilizations in the different streams others feel that this is an expensive product for one simple use case."
"New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS."
"Making it more user-friendly would be an improvement."
"For the workloads that are not too high, appliance is a little bit expensive."
"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."
"Scripting needs improvement. It's hard for our customers."
"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product. Sometimes, when the customer use case is just a very small subset of what's being offered in IBM DataPower Gateway, then the product can be expensive, making my company lose some of the opportunities because of the expensive pricing. A lower price point for IBM DataPower Gateway, even if that results in a less feature-rich version, would be appreciated. In terms of additional features that I'd like to see in the next release of IBM DataPower Gateway, nothing specific comes to mind because IBM constantly improves its standards and provides quarterly updates to the product, so it's quite fine."
"I find the installation configuration is quite difficult compared to other solutions."
"The images and size of the containers are too big and I think that they should be more lightweight."
"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."
"The user interface is designed mainly for experts, much in the way a BPM or another integration tool is."
"They are expensive and not worth the money we are spending on them."
"There is some lag in the GUI. There have been some performance issues and maybe it's because of the application data."
"Today I probably wouldn't go for Message Broker because of the cost structure, support, and the whole ecosystem around IBM."
"My biggest complaint about this product is the price."
 

Pricing and Cost Advice

"The cost is very high and requires all five components in the API management solution."
"It is an expensive solution."
"The solution is expensive in comparison to other products."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"The solution has a return on investment but is a little 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."
"The tool's initial costing is expensive for small banks and financial institutions."
"The licensing cost is very expensive."
"The solution is expensive."
"IBM software can be costly, but having a contract has helped manage and potentially lower costs over time."
"The licensing cost of IBM WebSphere Message Broker needs to be reduced"
"The solution is expensive."
"I feel with IBM, when you want certain functions or features, you have to continuously purchase add-ons. There are always additional fees."
"The price is very high and it's the main reason that we are searching for alternatives."
"This product is more expensive than competing products."
"IBM products are generally more stable and have more features, but also come at a greater cost."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
893,244 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%
Financial Services Firm
21%
Construction Company
13%
Computer Software Company
9%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise18
By reviewers
Company SizeCount
Small Business2
Large Enterprise10
 

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 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...
What is your primary use case for IBM WebSphere Message Broker?
We use the product for exposing services at the application level, integrating with various architectures like WebSphere, and handling static service creation.
 

Also Known As

WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower
WebSphere Message Broker
 

Overview

 

Sample Customers

RBL Bank, Availity
WestJet, Blue Cross and Blue Shield of North Carolina, Sharp Corporation, Michelin Tire
Find out what your peers are saying about IBM DataPower Gateway vs. IBM WebSphere Message Broker and other solutions. Updated: April 2026.
893,244 professionals have used our research since 2012.