We performed a comparison between IBM Cloud Pak for Integration and IBM DataPower 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."The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."
"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
"It is a stable solution."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"The solution is straightforward and for large organizations, it functions well."
"It's high-speed and it can be remotely administered via an API."
"The solution is very easy to work with."
"It is a scalable solution."
"Since it is a gateway, it provides a lot of security features."
"The solution is robust."
"It is easy to use, easy to install, and it's resilient for high availability."
"The performance is good. It's been very stable."
"The initial setup is not easy."
"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."
"The pricing can be improved."
"Its queuing and messaging features need improvement."
"They should improve the solution's clustering features."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"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 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."
"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."
"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."
More IBM Cloud Pak for Integration Pricing and Cost Advice →
IBM Cloud Pak for Integration is ranked 21st in API Management with 4 reviews while IBM DataPower Gateway is ranked 8th in API Management with 26 reviews. IBM Cloud Pak for Integration is rated 8.6, while IBM DataPower Gateway is rated 8.4. The top reviewer of IBM Cloud Pak for Integration writes "A hybrid integration platform that applies the functionality of closed-loop AI automation". On the other hand, the top reviewer of IBM DataPower Gateway writes "Easy to use, plenty of functionality, but expensive". IBM Cloud Pak for Integration is most compared with IBM App Connect, IBM API Connect, MuleSoft Anypoint API Manager, Microsoft Azure API Management and AWS Glue, whereas IBM DataPower Gateway is most compared with IBM API Connect, Apigee, Microsoft Azure API Management, Mule ESB and NGINX Plus. See our IBM Cloud Pak for Integration vs. IBM DataPower 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.