We performed a comparison between Microsoft Azure API Management and Apigee based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Based on the parameters we compared, Apigee received higher ratings than Microsoft Azure API Management. Although Apigee is the more expensive solution, it comes out on top with more favorable features and good technical support.
"The analytics function and the developer portal are the two valuable features of Apigee. The analytics part is very good, and the developer portal is quite rich in features."
"Apigee has better scalability than WSA."
"Its customer service is good."
"Apigee is a very lightweight solution."
"The flexibility allows you to quickly run a cloud-native application architecture."
"Highly scalable from any initial topology to horizontal extension"
"Its flexibility allows seamless management of different products, showcasing scalability to handle extensive solutions."
"The initial setup isn't too complex."
"I like the API Management functions."
"We're very satisfied with Azure API Management. We've had no issues with bugs, everything runs smoothly, and the connection between the cloud and the on-premise infrastructure was good."
"We use this solution for API rate limiting and for its security features against DDoS."
"The mediation and translation from SOAP to REST technology makes it possible to open up legacy systems that couldn't be opened before."
"It's easy to use compared to other products. It's easy to set up."
"The most valuable feature of Microsoft Azure API Management is monitoring. When compared with Apigee, I prefer Microsoft Azure API Management."
"The most valuable feature is the developer portal, which has source code examples in various programming languages to help developers learn the API."
"Most of the features are valuable to me."
"Access restrictions can be improved."
"Development IDE, especially for Architect Review."
"Unlike WSA, Apigee does not have a partnership model, something which makes it a bit easier for companies such as ours to go with the former solution."
"When there is an update on a new version or an automatic update, you have to be present and double-check that the update is reflected in the environment with no issues."
"Apigee is demanding on the infrastructure so the setup cost is very high for an on-premises deployment."
"In terms of the functionalities of a typical API gateway, Apigee is actually doing its job, but when it involves integration with backend applications, which some gateways have, I don't believe it has this functionality. You have to do Java or do some other low-level coding before you are able to do the integration. Apigee has a lot of components, which means that management will be a bit difficult. It probably has ten different components, and all of these components leverage open-source utilities, such as NGINX. When those open-source vendors upgrade their utility, Apigee usually lags behind because they need to do a lot of tests and any required development in their own platform. They need to do rigorous testing to make sure that nothing breaks. Because of that, it takes them a while to upgrade whatever components have been upgraded by the open-source vendor that owns the utility. We've been chasing them for a particular upgrade for well over a year and a half, and they have not done that upgrade. It is creating a security risk for us as an enterprise, but that upgrade has not been done, even though the open-source vendor, the owner of the utility, has upgraded it a long time ago."
"One feature they have to invest time into is the developer portal they use."
"Role-based access management needs to be improved. It would also be nice if the solution could be integrated with code versioning systems like Git/Bitbucket."
"Microsoft Azure API Management is lagging behind Apigee and should also have a better CICD process."
"In terms of improvement, it would be helpful if they could develop an on-premises option."
"The portal where we publish the APIs could be improved. Maybe this is because we didn't configure it. It is quite easy to bypass API management because we have a lot of information shared on the portal, where we publish our APIs. I worry there is potential for a security breach in the API publishing. There needs to be more security available on terms of the way we publish them."
"From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance."
"If I compare this solution to others I have used in other phases of my life, having APIM being an Azure resource, it is easy to configure and deploy. However, this conversely reduced the flexibility. The difficulty is how do we configure it in a manner that a larger enterprise would probably want it to be. This creates a bit more complexity, working around the constraints of the resource itself. If comparing it to other solutions, it is more of a legacy design with an older approach. The various level components are still around resembling an on-premise type of design similar to other solutions, such as Apigee or Mulesoft. They are still predominantly carrying some legacy design. Which might be suited for organizations where they have a more complex network layout. APIM is easy to deploy, but on the other side of that, it is constrained to how Azure has designed it to be."
"The developer console for external users could be improved, especially in the testing site."
"The product needs to introduce a developer portal."
"I rate the technical support from Microsoft Azure API Management a four out of five."
More Microsoft Azure API Management Pricing and Cost Advice →
Apigee is ranked 2nd in API Management with 82 reviews while Microsoft Azure API Management is ranked 1st in API Management with 68 reviews. Apigee is rated 8.2, while Microsoft Azure API Management is rated 7.8. The top reviewer of Apigee writes "Has a robust community and outstanding performance". On the other hand, the top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". Apigee is most compared with IBM API Connect, Amazon API Gateway, WSO2 API Manager, Layer7 API Management and MuleSoft Anypoint API Manager, whereas Microsoft Azure API Management is most compared with Amazon API Gateway, MuleSoft Anypoint API Manager, Kong Gateway Enterprise, IBM API Connect and WSO2 API Manager. See our Apigee 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.