We performed a comparison between Amazon API Gateway and Microsoft Azure API Management based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Azure is highly regarded for its stability, integration capabilities, and user-friendliness, whereas Amazon is appreciated for its flexibility and ease of use. Azure users express a desire for lower licensing fees, improved integration, and enhanced performance, while Amazon users seek better monitoring and security features. Azure's pricing is considered reasonable but could be more cost-effective, while Amazon's pricing is generally acceptable. The quality of Azure's technical support varies, while Amazon's support is generally satisfactory.
"It's easy to integrate and provide support for existing AWS services if I use the AWS API gateway."
"Its security feature is the most valuable because it is mainly a security solution. It has easy authentication and authorization, and its integration is also useful."
"Amazon API Gateway can integrate with ECS and Lambda."
"Integrating API Gateway with other AWS services was easy. It worked out of the box, so it worked perfectly."
"The most valuable feature is it has lots of integration."
"It's flexible. It was valuable."
"The solution is stable."
"This solution is useful for making new APIs."
"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."
"Monitoring: It gives us a detailed overview of how clients are using the API and it allows us to see the consumption trends in real-time."
"We use this solution for API rate limiting and for its security features against DDoS."
"I like the support they provide for the APIs more than the solution itself. First of all, documentation-wise, both Microsoft Azure and even Google Cloud are up there. But in comparison, the real-time consulting and support for APIs make Microsoft stand out a little. I also like the performance. Standard public cloud provider-built APIs are more resilient and flexible in terms of what feature you want to use and what feature you don't want to use, and they're more customizable. They are more resilient in terms of performance in that particular environment because that is the design aspect of the offering. When public clouds build APIs and deploy them after testing them on their framework for a certain amount of time, I feel there is a massive difference in the product's performance. On the interface, everything is strong."
"Azure API is scalable."
"Initial setup was quite easy."
"The package as a whole is useful for our customers."
"This solution is very flexible, and it's very compatible with the other Azure products."
"Amazon API Gateway needs to focus on minimizing latency."
"The solution could improve signature validation."
"The course management needs improvement. It's always an issue to set up the course management, especially when you use data form."
"We would like to see more UI-based monitoring."
"Monitoring could be improved."
"If I take into consideration the past three to four years, during which I used the tool, I would say that some missing and external configurations were not possible in the product, and it was a bit difficult to manage."
"I believe that there could be more features associated with analytics since it is an area where the product lacks."
"The API Gateway lacks the capability to directly facilitate API strategy development or user onboarding workflows."
"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."
"Multi-tenant functionalities is missing from the system, especially when it comes to the developer code of features."
"Microsoft Azure API Management could improve by having better integration with third-party solutions."
"They should improve the inbuilt policies that they have and that should properly create a deployment architecture as well."
"The licensing fees should be cheaper."
"Some of the DevOps stuff could be easier to work with. The migration paths are a little complicated, and moving code around could be more seamless. There should be less manual migration when several teams work together to publish code to the DevOps."
"API Management's price could be lower."
"The implementation has room for improvement and can be more user-friendly."
More Microsoft Azure API Management Pricing and Cost Advice →
Amazon API Gateway is ranked 3rd in API Management with 37 reviews while Microsoft Azure API Management is ranked 1st in API Management with 67 reviews. Amazon API Gateway is rated 8.2, while Microsoft Azure API Management is rated 7.8. The top reviewer of Amazon API Gateway writes "Easy initial setup and highly stable solution". On the other hand, the top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". Amazon API Gateway is most compared with MuleSoft Anypoint API Manager, Apigee, WSO2 API Manager, Kong Gateway Enterprise and Layer7 API Management, whereas Microsoft Azure API Management is most compared with Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise, IBM API Connect and WSO2 API Manager. See our Amazon API 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.
