We performed a comparison between Microsoft Azure API Management and WSO2 API Manager based on our users’ reviews in four categories. After reading the collected data, you can find our conclusion below.
Comparison Results: Many users are heavily invested in Microsoft Azure products, making Microsoft Azure API Management more widely used and trusted. Additionally, WSO2 API lacks some new features and updated functionalities that other API solutions commonly provide. In terms of pricing, however, users are happier with WSO2.
"Everything is already available and ready to operate without a lot of preparation work."
"It’s easy to set up."
"It's very well integrated with the Azure environment."
"The most valuable feature of Microsoft Azure API Management is monitoring. When compared with Apigee, I prefer Microsoft Azure API Management."
"I like API Management's ability to do hybrid cloud stuff."
"The initial setup is not that complex, but there are certain challenges."
"I have found this solution to be easy to configure, simple to use, and flexible."
"Microsoft Azure API Management is better because it has a DevOps integration by default."
"WSO2 API Manager's most valuable features are the simple interface that is easy to use and the APIs lifecycle."
"The scalability is fine for our purposes."
"The main feature — the publication of the API, the management section — is great in general."
"A complete integration suite and a good platform."
"WSO2 API Manager is easy to use."
"Functionality-wise, I like WSO2 API Manager - Publisher API and WSO2 Enterprise Service Bus."
"The solution is open source and easy to configure."
"This is a flexible and versatile API management solution that has the power to integrate with more than just API."
"Azure is our most expensive resource; it's costly."
"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."
"The solution’s security and performance could be improved."
"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."
"The cloud deployment performance could be better."
"The integration with other API gateways is where they might try to improve."
"Specific to API development, I think Microsoft is still far behind AWS. AWS has grown by leaps and bounds, and Microsoft is a close second. But in terms of features and other stuff they provide, Microsoft's compatibility with publicly available APIs is a little limited. So, that is a little bit of a constraint. But what they provide is good, it's just that they need to build more on their API suite. I think Google is doing a really good job at that."
"It can be quite complex, somewhat lacking in flexibility."
"We had some problems with the reverse proxy not being able to invoke fully qualified domain names, so we have to build some custom scripts to solve this issue."
"Basically, mTLS is a certificate-based communication protocol that WSO2 API Manager doesn't support."
"The product hasn’t been updated for some time."
"WSO2 API Manager could improve the API approval system."
"API Manager is not easy to scale because some of its components lack scalability. It's a difficult point. Especially because companies are so cloud-based these days, microservice scalability is a major thing."
"Integration is an area that needs to be improved."
"The initial setup can be difficult."
"I would like it to be a more stable solution. Maybe in the last version that is approved. For me it would be good if they had a community established version."
More Microsoft Azure API Management Pricing and Cost Advice →
Microsoft Azure API Management is ranked 1st in API Management with 67 reviews while WSO2 API Manager is ranked 7th in API Management with 33 reviews. Microsoft Azure API Management is rated 7.8, while WSO2 API Manager is rated 8.0. The top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". On the other hand, the top reviewer of WSO2 API Manager writes "Reliable with good capabilities and good support". Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and IBM DataPower Gateway, whereas WSO2 API Manager is most compared with Apigee, Kong Gateway Enterprise, Amazon API Gateway, Apache APISIX and 3scale API Management. See our Microsoft Azure API Management vs. WSO2 API Manager 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.
