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."Azure API Management is an API gateway that can be used for different purposes, for example, to monetize APIs."
"Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation."
"I like API Management's ability to do hybrid cloud stuff."
"The integration with Azure Active Directory is a good security feature for authentication and authorization. There is multifactor authentication. You can also use all of the Azure AD features integrated with API Management."
"The most valuable features of Microsoft Azure API Management are the easy configuration and deployment with automation."
"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."
"The API management is great."
"Ease of integration into the entire Microsoft environment."
"The developer portal is a valuable feature."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."
"There were no complexities involved in the setup phase...The product is able to meet my company's API protection needs."
"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."
"I like the solution's policies, transformation, mediation, and routing features."
"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."
"It's a good tool, and it has a stable messaging broker."
"There is a limitation of 32 kb of data in the APIs. Having the limitation increase would be a benefit."
"They should improve the inbuilt policies that they have and that should properly create a deployment architecture as well."
"In the next release, Azure APIM should include deployment in various environments and CI/CD for deployment."
"Microsoft Azure API Management could improve by having better integration with third-party solutions."
"They're trying to implement versioning and trying to be able to manage different versions of your API all at the same time, but they're not doing that just quite right yet."
"What would make Microsoft Azure API Management better are more APIs. They keep updating their APIs, but it would be better if the solution had more APIs for the services and more integration with other platforms."
"Support for GraphQL could be better."
"They need to work on the third party integrations."
"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."
"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."
"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."
"It is an expensive solution and not very suitable for smaller businesses."
"The price has room for improvement."
"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."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
More Microsoft Azure API Management Pricing and Cost Advice →
Microsoft Azure API Management is ranked 1st in API Management with 68 reviews while webMethods API Gateway is ranked 11th in API Management with 10 reviews. Microsoft Azure API Management is rated 7.8, while webMethods API Gateway is rated 8.2. 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 WSO2 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.