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
7th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
31
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
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 February 2026, in the Enterprise Service Bus (ESB) category, the mindshare of IBM DataPower Gateway is 5.3%, down from 5.9% compared to the previous year. The mindshare of IBM WebSphere Message Broker is 4.7%, up from 4.0% 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 Gateway5.3%
IBM WebSphere Message Broker4.7%
Other90.0%
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 scalability of the solution is good."
"The API Connect gateway service and the SQL injection feature is good."
"It is a scalable solution."
"The solution is straightforward and for large organizations, it functions well."
"The most valuable feature is the security appliance, it's very secure."
"I like that it is very stable, and we never experience any downtime."
"The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
"I like the API Gateway feature."
"The transactions and message queuing are the most valuable features of the solution."
"Integration and mapping are easy, which is a major advantage."
"IBM WebSphere Message Broker is one of the best middleware solutions"
"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."
"The solution has good integration."
"Straightforward development and deployment."
"The documentation, performance, stability and scalability of the tool are valuable."
"It has many interfaces and you can connect to any backend source that has another format, and convert it to the desired format."
 

Cons

"From the development perspective, it has limitations because it only supports the XSLT language. It does not support multiple languages."
"Its support services could be better."
"The DCDR process should be less complex."
"They should add features to manage API integrations."
"We are always looking for more features wherein it could be easily integrated with cloud applications. We are looking for either a cloud solution or a cloud integration option."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"The user interface or the application development perspective and customization of the tool could be a little better."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"Stability and pricing are areas with shortcomings that need improvement."
"Today I probably wouldn't go for Message Broker because of the cost structure, support, and the whole ecosystem around IBM."
"Technical support is very slow and needs to be improved."
"Technical support is good but they could have a better response time."
"The product's features are not being upgraded or enhanced by the vendor"
"The installation configuration is quite difficult."
"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."
"There is some lag in the GUI. There have been some performance issues and maybe it's because of the application data."
 

Pricing and Cost Advice

"It's expensive when you compare it with others."
"The solution is expensive in comparison to other products."
"It is an expensive solution."
"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."
"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."
"The licensing cost is very expensive."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"I feel with IBM, when you want certain functions or features, you have to continuously purchase add-ons. There are always additional fees."
"IBM products are generally more stable and have more features, but also come at a greater cost."
"The solution is expensive."
"The price is very high and it's the main reason that we are searching for alternatives."
"The solution is expensive."
"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 licensing cost of IBM WebSphere Message Broker needs to be reduced"
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
881,733 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Insurance Company
9%
Manufacturing Company
8%
Computer Software Company
7%
Financial Services Firm
22%
Computer Software Company
11%
Insurance Company
9%
Transportation 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 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?
The developer portal should be an integrated part of IBM DataPower Gateway to improve it. I think it is fine as is, and maybe no other additional features should be included in the next release. My...
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: February 2026.
881,733 professionals have used our research since 2012.