We performed a comparison between IBM DataPower Gateway and webMethods API Gateway based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Since it is a gateway, it provides a lot of security features."
"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."
"It is very easy to set up and configure, even for users with no prior experience."
"The API Connect gateway service and the SQL injection feature is good."
"The performance is good. It's been very stable."
"The product is stable...The product is scalable."
"My company has a good impression of IBM DataPower Gateway. What I like about it is that because it's an appliance, it's a turnkey solution that's very fast and out of the box. Compared to other gateways, I also like that IBM DataPower Gateway is function-rich. For example, for one of the projects, there was a need for specific transformation and security features available in IBM DataPower Gateway out of the box, so my team just needed to configure the appliance. There was no need for separate development, and I found it quite neat. Another valuable feature of IBM DataPower Gateway is that it's easy to integrate with other products."
"It is a scalable solution."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"The cloud version of the solution is very easy to set up."
"I like the solution's policies, transformation, mediation, and routing features."
"It's a good tool, and it has a stable messaging broker."
"The developer portal is a valuable feature."
"This solution has given us a competitive advantage because we have better automation and insight."
"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."
"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."
"Its support services could be better."
"In the next release, I would like to see the product price reduced. It should be cheaper."
"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."
"Scripting needs improvement. It's hard for our customers."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"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."
"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."
"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."
"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."
"They should develop clear visibility for the onboarding."
"Understanding the overall architecture is difficult."
"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."
"The price has room for improvement."
"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."
"The high price of the product is an area of concern where improvements are required."
"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."
IBM DataPower Gateway is ranked 7th in API Management with 27 reviews while webMethods API Gateway is ranked 11th in API Management with 10 reviews. IBM DataPower Gateway is rated 8.4, while webMethods API Gateway is rated 8.2. The top reviewer of IBM DataPower Gateway writes "Easy to use, plenty of functionality, but expensive". On the other hand, the top reviewer of webMethods API Gateway writes "We developed several services in the cloud using a sandbox environment for our last hackathon". IBM DataPower Gateway is most compared with IBM API Connect, Apigee, Microsoft Azure API Management, Mule ESB and IBM Integration Bus, whereas webMethods API Gateway is most compared with Apigee, webMethods.io Integration, Kong Gateway Enterprise, 3scale API Management and webMethods Microgateway. See our IBM DataPower Gateway vs. webMethods API Gateway report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
