We performed a comparison between IBM DataPower Gateway and Microsoft Azure API Management 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."It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"It's high-speed and it can be remotely administered via an API."
"What I like most is the stability."
"I like all of the features in this product and it does what it's supposed to do."
"The solution is stable."
"Support for PCA and non-PCA services is valuable."
"It is easy to use, easy to install, and it's resilient for high availability."
"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."
"I like the stability and the ease of use."
"Initial setup was quite easy."
"I have found this solution to be easy to configure, simple to use, and flexible."
"Allows the possibility of VPN technology to connect your gateway directly with on-prem services"
"It's easier to use and has more features than Google."
"It’s easy to set up."
"It's a very robust tool. So you see that there is a developer portal which can be used by developer or the vendors as well. And other external partners to create keys and manage their own APIs. The other thing is that they have a lot of policies there are too many options within API. So I do the difficult to tell one, but probably I would say, like, proxy sorry. The policies is one of the thing wherein you can just configure the policies and modify the behavior of the APIs."
"Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation."
"The initial setup isn't so easy, you need who has experience working with the solution to help."
"The programming language is only supported in XSLT and Gateway script."
"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."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"I would like the tool to improve its training."
"They should improve the solution's clustering features."
"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."
"Support for GraphQL could be better."
"The licensing tiers can be misleading."
"The implementation has room for improvement and can be more user-friendly."
"It would be better if it were easier to transition to Azure from JIRA. For example, different nomenclature must be performed when you shift to Azure from JIRA. JIRA's storage, tasks, and ethics are treated differently from Azure. Here they might become functions, which is not an option in JIRA because that nomenclature difference is there. If someone has to get into the nomenclature, then there can be different tasks from clients, and here, they may be treated as functions. JIRA has sub-tasks, but sub-tasks don't exist in Azure. The nomenclature and the linking between ethics and a function and a story are different, and people may have to learn to adapt to the new nomenclature."
"Microsoft Azure API Management should have the ability to allow multitenancy."
"The integration with other API gateways is where they might try to improve."
"I could that the UI could be improved."
"There is room for improvement in the user interface and workflow for hosting APIs, especially third-party APIs."
More Microsoft Azure API Management Pricing and Cost Advice →
IBM DataPower Gateway is ranked 7th in API Management with 27 reviews while Microsoft Azure API Management is ranked 1st in API Management with 68 reviews. IBM DataPower Gateway is rated 8.4, while Microsoft Azure API Management is rated 7.8. The top reviewer of IBM DataPower Gateway writes "Security features meets compliance needs and offers MPGW (Multi-Protocol Gateway) that simplifies integration efforts ". On the other hand, the top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". IBM DataPower Gateway is most compared with IBM API Connect, Apigee, Mule ESB, IBM Integration Bus and Kong Gateway Enterprise, whereas Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and SwaggerHub. See our IBM DataPower Gateway vs. Microsoft Azure API Management 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.
