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.
"One of the most valuable aspects of API Gateway is its native integration with AWS services."
"It's flexible. It was valuable."
"t is easy for integrations if it is deployed in AWS Services."
"It is easy to set up. It is also quick to deploy."
"Amazon stack is easy to use in combination with other Amazon services, so it was a logical continuity."
"In terms of most valuable features, it would say that it is really easy to start working with it."
"The best thing about Amazon API Gateway is that it can authenticate and authorize requests without going to our back end."
"What I like best about Amazon API Gateway is that it's simple to use, easy to set up, and you can quickly get it up and running. It's a very user-friendly solution. I also didn't experience any issues in terms of Amazon API Gateway interface, integration, or monitoring. The solution runs smoothly."
"The tool helps to manage APIs."
"The mediation and translation from SOAP to REST technology makes it possible to open up legacy systems that couldn't be opened before."
"Microsoft Azure API Management is 90 to 99 percent scalable. We have three instances running in parallel."
"Access control is the most valuable aspect."
"Most of the features are valuable to me."
"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."
"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."
"The initial setup is not that complex, but there are certain challenges."
"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."
"The integration could be improved."
"It's hard to configure. There's a lot of options but it's very hard, it's very confusing."
"Its support for SAM integration could be made more accessible."
"The user interface could be improved, as well as customer support and having a local customer representative in a country."
"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."
"API Gateway lacks some governance features that MuleSoft offers, and there are additional features that could make it even better."
"The developer console for external users could be improved, especially in the testing site."
"When you start with Azure API management, you also need to onboard the Azure console and the Azure cloud environment, which comes with a price."
"Security could be improved."
"Sometimes when immediate support is required, it isn't available."
"From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance."
"Maybe the customization could be a bit better."
"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."
"There is always room for improvement. There should be more analytics abilities so you can know how much traffic there is. Log Analyzer isn't well integrated with this solution."
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.