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

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)
5th
Ranking in Application Infrastructure
12th
Average Rating
8.4
Reviews Sentiment
6.5
Number of Reviews
30
Ranking in other categories
SOA Application Gateways (1st), API Management (12th)
IBM WebSphere Message Broker
Ranking in Enterprise Service Bus (ESB)
9th
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 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 WebSphere Message Broker is 4.0%, down from 4.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Market Share Distribution
ProductMarket Share (%)
IBM DataPower Gateway6.6%
IBM WebSphere Message Broker4.0%
Other89.4%
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.
BrajendraKumar - PeerSpot reviewer
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 API Connect gateway service and the SQL injection feature is good."
"I like the API Gateway feature."
"The product is stable...The product is scalable."
"The solution is straightforward and for large organizations, it functions well."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"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 solution is very easy to work with."
"I like the API Gateway feature."
"The documentation, performance, stability and scalability of the tool are valuable."
"We only use the basic features, but the most valuable one for us is the Publish-subscribe pattern."
"It's reliable for our day-to-day operations, ensuring fast and secure data integration across different systems."
"The transactions and message queuing are the most valuable features of the solution."
"Message Broker is valuable because most of the applications are using MQ. Even in my current engagement, the few applications which I audit to onboard the bank are using MQ."
"The solution has good integration."
"Integration and mapping are easy, which is a major advantage."
"Straightforward development and deployment."
 

Cons

"The product should be more adapted to the DevOps process."
"The user interface or the application development perspective and customization of the tool could be a little better."
"Additional documentation needs to be provided for complex automations."
"The initial setup isn't so easy, you need who has experience working with the solution to help."
"Making it more user-friendly would be an improvement."
"The DCDR process should be less complex."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"Technical support is very slow and needs to be improved."
"Stability and pricing are areas with shortcomings that need improvement."
"Technical support is good but they could have a better response time."
"The installation configuration is quite difficult."
"The solution can add container engines such as docker."
"It is currently a weighty product."
"Today I probably wouldn't go for Message Broker because of the cost structure, support, and the whole ecosystem around IBM."
"The images and size of the containers are too big and I think that they should be more lightweight."
 

Pricing and Cost Advice

"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 licensing cost is very expensive."
"It is an expensive solution."
"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."
"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 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."
"I feel with IBM, when you want certain functions or features, you have to continuously purchase add-ons. There are always additional fees."
"The licensing cost of IBM WebSphere Message Broker needs to be reduced"
"The solution is expensive."
"IBM products are generally more stable and have more features, but also come at a greater cost."
"IBM software can be costly, but having a contract has helped manage and potentially lower costs over time."
"This product is more expensive than competing products."
"The price is very high and it's the main reason that we are searching for alternatives."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
868,706 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Insurance Company
9%
Computer Software Company
8%
Manufacturing Company
7%
Financial Services Firm
20%
Computer Software Company
10%
Insurance Company
9%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise16
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?
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...
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: September 2025.
868,706 professionals have used our research since 2012.