We performed a comparison between Apigee, Microsoft Azure API Management, and MuleSoft Anypoint API Manager based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Google, Amazon Web Services (AWS) and others in API Management."I use it because it's simple, it automatically updates, and It hasn't given me any issues."
"They capture the details of all the incoming and outgoing traffic of your APIs. Based on 300+ default dimensions you can generate beautiful and insightful reports on usage and consumption of APIs."
"The usability is one of the best aspects of the product."
"The security that you have with Apigee is very good and aligns with compliance."
"The initial setup isn't too complex."
"The use case which I have installed serves the intended purpose."
"The most valuable features of Apigee for me are analytics, security, ease of use, and integration capabilities."
"I have not encountered instability with the product."
"The product gives API gateway-related features, like throttling, which are easy to use and low-code/no-code."
"The price is pretty reasonable for us."
"It seems quite good so far. It handles our current workload well, and I'm optimistic it can scale effectively as our needs grow."
"API Management does not take long to deploy."
"There were no scalability issues."
"Azure API is scalable."
"The Application Gateway we have found to be the most useful in Microsoft Azure API Management. We have integrated the Microsoft Azure API Management with Application Gateway. Application Gateway is a type of load balancer that we are using for the high availability of our API calls."
"The tool's most valuable feature is the integration of CI/CD with the API gateway."
"Anypoint is very capable in terms of scalability."
"MuleSoft has given the API solution a 3-tiered architecture. This means that there are multiple channels available in one application. The usability is very high."
"MuleSoft Anypoint API Manager has the most valuable data components and can integrate APIs across multiple microservices."
"We use it heavily because Azure offers better pricing than its competitors."
"The tool has a private area. It also has a cloud deployment option."
"Technical support has been helpful."
"The entire offering and suite of tools that this solution provides have been very valuable. We are able to manage APIs on runtime on a cloud basis which has been very useful."
"Anypoint API Manager's most valuable feature is its connectors."
"Development IDE, especially for Architect Review."
"As it is now, the rotation of certificates is a manual task and is something that can be improved."
"Apigee is not a solution compatible with public clouds, making it one of its shortcomings where improvements are required."
"Integration should be improved."
"It needs predictive analysis of consumption."
"Apigee is more of an entry level solution that does basic things pretty well, but if you want to go more customizable, you want to really look for another solution."
"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."
"The solution could add even more functionalities."
"The external policies are impossible to look at and configure."
"I could that the UI could be improved."
"Microsoft Azure API Management's most valuable features are the microservices we used to use. They were API callers to receive communication with the network and building system, to complete the request. The response would be through the processing system."
"It would be better if it were easier to transition to Azure from JIRA. For example, different nomenclature must be performed when you shift to Azure from JIRA. JIRA's storage, tasks, and ethics are treated differently from Azure. Here they might become functions, which is not an option in JIRA because that nomenclature difference is there. If someone has to get into the nomenclature, then there can be different tasks from clients, and here, they may be treated as functions. JIRA has sub-tasks, but sub-tasks don't exist in Azure. The nomenclature and the linking between ethics and a function and a story are different, and people may have to learn to adapt to the new nomenclature."
"Microsoft Azure API Management needs to improve stability."
"The scalability of this solution could be improved. The volume which the API Management task service can handle needs to be improved. Cost wise, this solution could be optimized."
"Technical support could be more helpful and responsive."
"Microsoft Azure API Management is lagging behind Apigee and should also have a better CICD process."
"The dashboards in Mulesoft Anypoint API Manager could improve."
"Their analytics needs a lot of improvement. It's really lacking right now."
"The pricing is a bit expensive."
"I'd like more monitoring and analyzing features included in the future."
"One improvement is maybe to add a plugin in the API manager. Let's say an organisation is using SOAP services or legacy APIs. Maybe I don't want to migrate it to rest API, but my plugin should be able to convert Jason to XML. Basically, protocol transformation features in API Manager."
"To improve Anypoint API Manager for the next release, it should focus on better consumption scalability, especially for smaller APIs."
"In the next release, Mulesoft should make it easier for people who don't have the native connectors to build their own rather than using the APA from the power platform or outlet."
"Licensing costs should be reduced, it's quite expensive."
More Microsoft Azure API Management Pricing and Cost Advice →
More MuleSoft Anypoint API Manager Pricing and Cost Advice →