We performed a comparison between Microsoft Azure API Management 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."The most valuable feature of Microsoft Azure API Management is the developer portal because it's very quick and easy to get something published."
"Azure APIM's best features are its straightforward access management (it's a single point of access for all monitoring and logging and for policy implementation) and its integration with the Azure Cloud infrastructure."
"It's easy to use compared to other products. It's easy to set up."
"Ease of integration into the entire Microsoft environment."
"The tool's most valuable feature is the integration of CI/CD with the API gateway."
"The mediation and translation from SOAP to REST technology makes it possible to open up legacy systems that couldn't be opened before."
"The user management is pretty seamless."
"We're pretty much using all of the monetizations features out of the API manager so we can put up a portal and have a dev portal and then a prod portal and do rate limiting."
"The developer portal is a valuable feature."
"It's a good tool, and it has a stable messaging broker."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"I like the solution's policies, transformation, mediation, and routing features."
"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."
"This solution has given us a competitive advantage because we have better automation and insight."
"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."
"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 terms of improvement, it would be helpful if they could develop an on-premises option."
"Microsoft Azure API Management's most valuable features are the microservices we used to use. They were API callers to receive communication with the network and building system, to complete the request. The response would be through the processing system."
"The solution’s security and performance could be improved."
"There is a limitation of 32 kb of data in the APIs. Having the limitation increase would be a benefit."
"The product needs to introduce a developer portal."
"They should improve the inbuilt policies that they have and that should properly create a deployment architecture as well."
"Technical support could be more helpful and responsive."
"Multi-tenant functionalities is missing from the system, especially when it comes to the developer code of features."
"It is an expensive solution and not very suitable for smaller businesses."
"They should develop clear visibility for the onboarding."
"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 configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."
"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."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"Understanding the overall architecture is difficult."
"The price has room for improvement."
More Microsoft Azure API Management Pricing and Cost Advice →
Microsoft Azure API Management is ranked 1st in API Management with 67 reviews while webMethods API Gateway is ranked 12th in API Management with 9 reviews. Microsoft Azure API Management is rated 7.8, while webMethods API Gateway is rated 8.0. The top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". 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". Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and IBM API Connect, whereas webMethods API Gateway is most compared with Apigee, webMethods.io Integration, Kong Gateway Enterprise, webMethods Microgateway and MuleSoft Anypoint API Manager. See our Microsoft Azure API Management 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.
