We performed a comparison between Akana API Management and Microsoft Azure API Management 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."It allowed us to publish and replace pre-essential transactions in one place, with a uniformity in terms of control and policies."
"The tool's authentication mechanism is easy to implement. We had to define a few parameters."
"Good interface, intuitive solution."
"The solution has overall high performance."
"The package as a whole is useful for our customers."
"I like API Management's ability to do hybrid cloud stuff."
"The tool helps to manage APIs."
"This solution is very flexible, and it's very compatible with the other Azure products."
"It's very well integrated with the Azure environment."
"The tool's most valuable feature is the integration of CI/CD with the API gateway."
"The API management and the hosting of the API platform are great."
"The product has new features that we are going to implement in the next few months, such as API management and analytic reporting."
"Akana API Management needs to improve its documentation."
"Lacks an integrated billing feature."
"Microsoft Azure API Management should have the ability to allow multitenancy."
"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."
"There is a limitation of 32 kb of data in the APIs. Having the limitation increase would be a benefit."
"From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance."
"The product needs to introduce a developer portal."
"What would make Microsoft Azure API Management better are more APIs. They keep updating their APIs, but it would be better if the solution had more APIs for the services and more integration with other platforms."
"The API gateway can be very complex."
"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."
More Microsoft Azure API Management Pricing and Cost Advice →
Akana API Management is ranked 27th in API Management with 3 reviews while Microsoft Azure API Management is ranked 1st in API Management with 67 reviews. Akana API Management is rated 8.4, while Microsoft Azure API Management is rated 7.8. The top reviewer of Akana API Management writes "Authentication mechanism is easy to implement but improvement is needed in documentation ". On the other hand, the top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". Akana API Management is most compared with Apigee, MuleSoft Anypoint API Manager, Amazon API Gateway, Kong Gateway Enterprise and IBM API Connect, whereas Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and IBM API Connect.
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.
