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."The solution is stable."
"The product's most valuable features are AAA policies and security features."
"The product is stable...The product is scalable."
"I like all of the features in this product and it does what it's supposed to do."
"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."
"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."
"Support for PCA and non-PCA services is valuable."
"The performance is good. It's been very stable."
"It is easy to use."
"The tool's most valuable feature is the integration of CI/CD with the API gateway."
"The initial setup is not that complex, but there are certain challenges."
"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."
"The API management and the hosting of the API platform are great."
"The solution has overall high performance."
"The solution is reliable and very stable."
"Without a doubt, it has a very robust, strong marketplace where we can directly integrate with existing APIs and begin working on those."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"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."
"In the next release, I would like to see the product price reduced. It should be cheaper."
"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."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"Making it more user-friendly would be an improvement."
"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product. Sometimes, when the customer use case is just a very small subset of what's being offered in IBM DataPower Gateway, then the product can be expensive, making my company lose some of the opportunities because of the expensive pricing. A lower price point for IBM DataPower Gateway, even if that results in a less feature-rich version, would be appreciated. In terms of additional features that I'd like to see in the next release of IBM DataPower Gateway, nothing specific comes to mind because IBM constantly improves its standards and provides quarterly updates to the product, so it's quite fine."
"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."
"Specific to API development, I think Microsoft is still far behind AWS. AWS has grown by leaps and bounds, and Microsoft is a close second. But in terms of features and other stuff they provide, Microsoft's compatibility with publicly available APIs is a little limited. So, that is a little bit of a constraint. But what they provide is good, it's just that they need to build more on their API suite. I think Google is doing a really good job at that."
"One of the most important improvements for us would be if it supported the HTTP/3 version and new protocol over a quick connection."
"The user interface needs improvement."
"The implementation has room for improvement and can be more user-friendly."
"I'd like to have better flexibility and more capabilities."
"It can be quite complex, somewhat lacking in flexibility."
"The licensing fees should be cheaper."
More Microsoft Azure API Management Pricing and Cost Advice →
IBM DataPower Gateway is ranked 8th in API Management with 26 reviews while Microsoft Azure API Management is ranked 1st in API Management with 67 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 "Easy to use, plenty of functionality, but expensive". 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.