We performed a comparison between Microsoft Azure API Management and Tyk based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Microsoft Azure API Management has many valuable features. One is the developer portal, that's very useful for teams. The tool also provides layers of security. I also found the caching, automatic documentation, and version management functionalities most valuable."
"The initial setup is not that complex, but there are certain challenges."
"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."
"Access control is the most valuable aspect."
"It seems quite good so far. It handles our current workload well, and I'm optimistic it can scale effectively as our needs grow."
"The UI management is very easy to use."
"We use Microsoft due to the stability of the company."
"Most of the features are valuable to me."
"It is a good product for API management."
"The most valuable feature is the load balancing with the circuit-breaker function."
"You can set up workflows and write limited pieces of logic."
"The portal for developers that this solution provides has great functionality."
"The feature I find most valuable is that this solution allows us to manage our security."
"The scalability is very good. That was a key factor in the selection, like how it could be pushed to high volume and scalability, which seemed to be very good."
"The implementation has room for improvement and can be more user-friendly."
"Price is the first thing that comes to mind. It's quite expensive, which could be a barrier for some users."
"They should improve the inbuilt policies that they have and that should properly create a deployment architecture as well."
"The licensing fees should be cheaper."
"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."
"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."
"The hybrid part could be improved because API Management is entirely cloud-based, but some of our resources are on-prem, so formatting is an issue. Our goal is dual implementation."
"It should be easier to integrate."
"I would like to see some additional features like having some extensions for .NET core because we use it for our back-end language."
"Sometimes when new features are released, they are not immediately stable."
"We would like a better tool for generating documentation for the APIs to be developed."
"In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly better communication with the customer base that would be my main issue with them."
"We ran it for a while, but then we decided to move away from Tyk, because Tyk's cloud version, the SaaS version, has a significant limitation of limited flexibility, so you can't program very much."
"It is a young product and does not have the kind of brand recognition that would make it a more popular solution with our clients."
More Microsoft Azure API Management Pricing and Cost Advice →
Microsoft Azure API Management is ranked 1st in API Management with 68 reviews while Tyk is ranked 18th in API Management with 6 reviews. Microsoft Azure API Management is rated 7.8, while Tyk is rated 7.6. The top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". On the other hand, the top reviewer of Tyk writes "Simple to install, has many features, but lacks support for multiple programming languages". Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and IBM API Connect, whereas Tyk is most compared with Apache APISIX, Traefik Enterprise, Apigee, Amazon API Gateway and Gravitee. See our Microsoft Azure API Management vs. Tyk 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.