Try our new research platform with insights from 80,000+ expert users

Microsoft Azure API Management vs Tyk comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Microsoft Azure API Management
Ranking in API Management
1st
Average Rating
7.8
Number of Reviews
76
Ranking in other categories
No ranking in other categories
Tyk
Ranking in API Management
19th
Average Rating
7.6
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2024, in the API Management category, the mindshare of Microsoft Azure API Management is 20.9%, up from 20.5% compared to the previous year. The mindshare of Tyk is 1.9%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Allan Møller - PeerSpot reviewer
Sep 12, 2024
Transforms internal APIs with secure, manageable cloud compatibility
Our primary use case for Microsoft Azure API Management is to front internal APIs and make them cloud-compatible. It adds extra authentication on top of old APIs and acts as a proxy towards internal APIs, providing a single endpoint that can manage multiple APIs behind it. This is particularly…
MarkDoherty - PeerSpot reviewer
Jan 10, 2024
Fastest to get up and running and fewer idiosyncrasies than competitors
The common elements of the use case are a medium to a high volume of API calls, generally in a Microsoft-based environment, and occasionally Amazon. Implemented on the public cloud primarily for financial institutions. Serving retail clients with a reasonably complicated system architecture…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It's very well integrated with the Azure environment."
"The Azure Active Directory Synchronization is quite good."
"I like the support they provide for the APIs more than the solution itself. First of all, documentation-wise, both Microsoft Azure and even Google Cloud are up there. But in comparison, the real-time consulting and support for APIs make Microsoft stand out a little. I also like the performance. Standard public cloud provider-built APIs are more resilient and flexible in terms of what feature you want to use and what feature you don't want to use, and they're more customizable. They are more resilient in terms of performance in that particular environment because that is the design aspect of the offering. When public clouds build APIs and deploy them after testing them on their framework for a certain amount of time, I feel there is a massive difference in the product's performance. On the interface, everything is strong."
"The API management and the hosting of the API platform are great."
"The ease of use of the solution is excellent."
"The most valuable features of Microsoft Azure API Management are the easy configuration and deployment with automation."
"Allows the possibility of VPN technology to connect your gateway directly with on-prem services"
"It's easier to use and has more features than Google."
"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 portal for developers that this solution provides has great functionality."
"You can set up workflows and write limited pieces of logic."
"It is a good product for API management."
"The most valuable feature is the load balancing with the circuit-breaker function."
 

Cons

"API Management's price could be lower."
"In the next release, Azure APIM should include deployment in various environments and CI/CD for deployment."
"I rate the technical support from Microsoft Azure API Management a four out of five."
"The licensing tiers can be misleading."
"The user interface needs improvement."
"The integration with other API gateways is where they might try to improve."
"Security could be improved."
"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."
"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."
"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."
"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."
"Sometimes when new features are released, they are not immediately stable."
"I would like to see some additional features like having some extensions for .NET core because we use it for our back-end language."
 

Pricing and Cost Advice

"It's free for less than ten users. If you want to go beyond that, it's around $3.50 per user per month. If you want a DevOps integration, it's about $7.50 per user per month. Costs depend on the size, complexity, usage, and what facility you want to integrate. So, we use Microsoft Azure and have the entire DevOps and Visual Studio on the cloud. We get all three flavors for $7.50 per user per month."
"Since everyone is isocentric here, it is reasonable for me."
"Azure API Management is the most expensive solution on the market."
"Licensing fees are paid on an annual basis."
"The developer and standard pricing tiers of Azure API Management are very competitive compared to other products."
"Azure's pricing is very competitive compared to platforms like Apigee and MuleSoft."
"It is an expensive solution, but any API solution will be expensive."
"Azure is a pay-as-you-go model. You build out your virtual environment and pay a monthly price depending on CPU cores, storage, etc."
"We are using the open-source version of this product, so there are no licensing costs for its use."
"The price is low compared to other products of a similar type."
"It had a free version, which suited many of our needs, but not all, but we were happy to go ahead with the licensed version as well, which is the paid version."
"There are different versions and plans available depending on the requirements, so there is flexibility in terms of the pricing."
"The cost curve is far smoother, both in terms of volume and the number of calls it's running on, compared to most competitors. So it's a tad more expensive at the very low end, but the curve is nothing like Apigee or some of the others."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
815,854 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
14%
Manufacturing Company
9%
Insurance Company
7%
Financial Services Firm
23%
Computer Software Company
18%
Healthcare Company
7%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

How does Apigee differ from Azure API Management?
Apigee offers both cloud-based and on-prem options while Microsoft Azure API Management currently only offers a cloud-based solution. Both solutions are easy to use. Apigee allows for the ability...
Which is better - Azure API Management or Amazon API Gateway?
If you use Azure products, API Management is a great solution. It solves many of the problems of externalizing web services. For example, when you need versioning, establish a developer portal and ...
What do you like most about Microsoft Azure API Management?
Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation.
What do you like most about Tyk?
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.
What is your experience regarding pricing and costs for Tyk?
The pricing is actually quite competitive. In Azure environments, it gets beaten by Microsoft API Gateway, but on the other hand, it offers some features that Microsoft lacks. So it really comes do...
What needs improvement with Tyk?
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 ...
 

Also Known As

Azure API Management, MS Azure API Management
No data available
 

Learn More

Video not available
 

Overview

 

Sample Customers

adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH, Opensistemas
Trip Advisor, Juniper Networks, AT&T
Find out what your peers are saying about Microsoft Azure API Management vs. Tyk and other solutions. Updated: October 2024.
815,854 professionals have used our research since 2012.