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.
"The solution is solid, robust, and scalable."
"The solution is a managed service and requires minimal configuration, which makes it easy to launch an API."
"In terms of most valuable features, it would say that it is really easy to start working with it."
"All information and data needs to be sanitized before it enters a private domain and we use this solution to do this."
"Amazon API Gateway is a very fast solution."
"Amazon API Gateway can integrate with ECS and Lambda."
"It's flexible. It was valuable."
"The best thing about Amazon API Gateway is that it can authenticate and authorize requests without going to our back end."
"Everything is already available and ready to operate without a lot of preparation work."
"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 most valuable features of Microsoft Azure API Management are the easy configuration and deployment with automation."
"The most valuable feature of Microsoft Azure API Management is the developer portal because it's very quick and easy to get something published."
"The most valuable feature is the developer portal, which has source code examples in various programming languages to help developers learn the API."
"The documentation and configuration of APIs."
"It seems quite good so far. It handles our current workload well, and I'm optimistic it can scale effectively as our needs grow."
"I like API Management's sandbox feature. It's an environment where you can test out the API before putting it into production and connecting it to a live environment."
"It would be useful to have a more complete development environment for the developer, with different integrative capabilities to manage all the life cycles for the API. I think the full version formula for that is really useful. They should improve the development environment for easier integration."
"Amazon API Gateway will wait for only 30 seconds to get a response from other services, such as the Lambda function."
"We faced a few issues with the documentation."
"The tool's UI requires time to understand."
"When working with XML payloads, there can be issues due to the lack of a seamless connection between API Gateway and Lambda functions."
"The pricing could be improved. In cases where customers require real-time sync or real-time calling groups with IoT, the volume of data and time lag become a concern."
"I am not completely satisfied with Technical Support."
"I believe that there could be more features associated with analytics since it is an area where the product lacks."
"An area for improvement in Microsoft Azure API Management is deployment, in particular, the deployment of versions in Oryx. The development to production instance isn't adequate for me and needs to be improved. Microsoft Azure API Management lacks automation, which is another area for improvement."
"The hybrid part could be improved because API Management is entirely cloud-based, but some of our resources are on-prem, so formatting is an issue. Our goal is dual implementation."
"I would like to see better scalability and better performance."
"The product needs to introduce a developer portal."
"In the API you need to delete the suffix. It is annoying that you need to have a suffix. We can add a suffix at the API level, not at the operation level, and that could be improved on."
"They should improve the inbuilt policies that they have and that should properly create a deployment architecture as well."
"Price is the first thing that comes to mind. It's quite expensive, which could be a barrier for some users."
"Microsoft Azure API Management could improve the documentation. The documentation feels like marketing information and not sufficient technical information. Your easiest option is to purchase services from a Microsoft partner and this is their marketing."
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 68 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, Layer7 API Management and Kong Gateway Enterprise, 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.