Azure API Management vs. WSO2 API Manager

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure API Management
Score 8.3 out of 10
N/A
Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
WSO2 API Manager
Score 9.3 out of 10
Enterprise companies (1,001+ employees)
WSO2 API Manager makes it possible for developers to both develop and manage APIs of different types. Unlike solutions which focus only on managing API proxies, WSO2 API Manager provides tools to develop APIs by integrating different systems as well. It supports a variety of API types from REST, SOAP, GraphQL, WebSockets, WebHooks, SSEs and gRPC APIs with specialized policies and governance for each different type. Being fully open source, its architecture and extensibility…
$0
per month
Pricing
Azure API ManagementWSO2 API Manager
Editions & Modules
Consumption
0.042 per 10,000 calls
Lightweight and serverless version of API Management service, billed per execution
Developer
$48.04
per month Non-production use cases and evaluations
Basic
$147.17
per month Entry-level production use cases
Standard
$686.72
per month Medium-volume production use cases
Premium
$2,795.17
per month High-volume or enterprise production use cases
Isolated
TBA
per month Enterprise production use cases requiring high degree of isolation
No answers on this topic
Offerings
Pricing Offerings
Azure API ManagementWSO2 API Manager
Free Trial
NoNo
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoYes
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Features
Azure API ManagementWSO2 API Manager
API Management
Comparison of API Management features of Product A and Product B
Azure API Management
8.0
4 Ratings
2% below category average
WSO2 API Manager
8.8
4 Ratings
8% above category average
API access control8.94 Ratings9.54 Ratings
Rate limits and usage policies5.44 Ratings9.54 Ratings
API usage data8.94 Ratings8.04 Ratings
API user onboarding9.03 Ratings8.04 Ratings
API versioning8.94 Ratings9.04 Ratings
Usage billing and payments5.23 Ratings9.04 Ratings
API monitoring and logging9.84 Ratings8.54 Ratings
Best Alternatives
Azure API ManagementWSO2 API Manager
Small Businesses
NGINX
NGINX
Score 9.0 out of 10
NGINX
NGINX
Score 9.0 out of 10
Medium-sized Companies
NGINX
NGINX
Score 9.0 out of 10
NGINX
NGINX
Score 9.0 out of 10
Enterprises
NGINX
NGINX
Score 9.0 out of 10
NGINX
NGINX
Score 9.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Azure API ManagementWSO2 API Manager
Likelihood to Recommend
8.0
(4 ratings)
9.5
(4 ratings)
User Testimonials
Azure API ManagementWSO2 API Manager
Likelihood to Recommend
Microsoft
APIM is useful for the standard scenarios:
1) Securing your back-end APIs - If you have a legacy back-end web service that has a basic authentication scheme, you can add some additional security by placing APIM in front, and requiring subscription keys. Leverage your existing firewall to ensure only your APIM instance can communicate with your back-end API, and you've basically added a layer of protection.
2) Lift and shift - there are always going to be clients that don't want to update their clients to use a newer API; in some cases you can make a newer API look like an older one by implementing some complex policies in APIM. You can also do the opposite, making older APIs look new, such as making an XML back-end accept both JSON and XML.
3) Centralizing your APIs - if you've acquired another company and want to make their API set look as if it's a part of the larger whole, APIM is an easy way to provide a consistent front-end interface for developers.
Read full review
WSO2
It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?
Read full review
Pros
Microsoft
  • Easy commissioning of APIs.
  • Great policies to control access.
  • Easy mock services for testing.
Read full review
WSO2
  • Authentication based on OAuth 2.0 and HTTP Basic Authentication.
  • Rate Limiting applied at different levels like Subscriber, API, Resource and Backend.
  • Monitoring by exporting the metrics in Prometheus and traces in Jaeger.
  • Mediation to perform transformation, orchestration etc.
Read full review
Cons
Microsoft
  • Lack of robustness is a bit of an issue. Several other providers offer more options and capabilities, but then, they are lacking in interface ease.
  • As with anything Azure, pricing is really hard to stay on top of. I always find that you really don’t know what you’re paying for until you get the bill. Having an excellent Azure Administrator can help resolve that.
  • Integrating with app services outside of Azure can be a challenge, or at least much more challenging than just using Azure App Services.
Read full review
WSO2
  • Better QA testing prior to releases rollout
  • Better support needed
Read full review
Alternatives Considered
Microsoft
Azure APIM vs Amazon API Gateway:
1) Azure APIM was a complete package that included a developer portal.
2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.
3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway.
Read full review
WSO2
Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.
Read full review
Return on Investment
Microsoft
  • We can always think of positive ROI impact on business
  • It helps to easily facilitate the design, deployment, and maintenance of our APIs
Read full review
WSO2
  • We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
  • Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
  • Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.
Read full review
ScreenShots