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

IBM DataPower Gateway vs IBM WebSphere Message Broker comparison

Why PeerSpot?
 

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)
8th
Ranking in Application Infrastructure
13th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
SOA Application Gateways (1st), API Management (16th)
IBM WebSphere Message Broker
Ranking in Enterprise Service Bus (ESB)
10th
Ranking in Application Infrastructure
17th
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 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 IBM WebSphere Message Broker is 5.0%, up from 4.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway4.9%
IBM WebSphere Message Broker5.0%
Other90.1%
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

"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."
"The whole purpose of this product is to provide high speed and high performance."
"The API Connect gateway service and the SQL injection feature is good."
"The solution's technical support is excellent."
"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."
"The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
"It is very easy to set up and configure, even for users with no prior experience."
"I like that it is very stable, and we never experience any downtime."
"Performance-wise, this solution is really good."
"It has many interfaces and you can connect to any backend source that has another format, and convert it to the desired format."
"It is a scalable solution...The setup is easy."
"IBM WebSphere Message Broker is one of the best middleware solutions"
"Overall, in comparison to other solutions specific to the banking domain, this product is quite good."
"The solution has good integration."
"Integration and mapping are easy, which is a major advantage."
"Before the cloud, it was very easy for us to build and it was quick to integrate."
 

Cons

"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 IBM community does not have much engagement from the IT community in Saudi Arabia and developers for this solution are difficult to find."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"IBM DataPower Gateway is quite big for smaller organizations, looking at different types of clients who are virtually assisted in this, I would say it's not really a good product for smaller firms."
"They should add features to manage API integrations."
"Traceability could be improved, especially for business operations. The traceability of the transactions could be an improvement point for DataPower to work on. It would be better if they provided JSON support. JSON protocol data has changed format. It started performing internal transformation to JSONx. This might be an additional complexity."
"The DCDR process should be less complex."
"Making it more user-friendly would be an improvement."
"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."
"It is currently a weighty product."
"Technical support is good but they could have a better response time."
"I find the installation configuration is quite difficult compared to other solutions."
"Stability and pricing are areas with shortcomings that need improvement."
"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."
"Today I probably wouldn't go for Message Broker because of the cost structure, support, and the whole ecosystem around IBM."
 

Pricing and Cost Advice

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

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 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.
Ask a question
Earn 20 points
 

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: November 2026.
922,700 professionals have used our research since 2012.