Azure API Management vs. WSO2 Enterprise Service Bus

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure API Management
Score 8.5 out of 10
N/A
Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
WSO2 Enterprise Service Bus
Score 7.1 out of 10
Enterprise companies (1,001+ employees)
WSO2 says they have taken a fresh look at old-style, centralized ESB architectures, and designed their unique WSO2 Enterprise Service Bus from the ground up as the highest performance, lowest footprint, and most interoperable service oriented architecture (SOA) and integration middleware today. Additionally, the vendor says that by relying on their carbon technology the ESB is able to deliver a smooth start-to-finish project experience.N/A
Pricing
Azure API ManagementWSO2 Enterprise Service Bus
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 Enterprise Service Bus
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Azure API ManagementWSO2 Enterprise Service Bus
Top Pros
Top Cons
Features
Azure API ManagementWSO2 Enterprise Service Bus
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 Enterprise Service Bus
-
Ratings
API access control8.94 Ratings00 Ratings
Rate limits and usage policies5.44 Ratings00 Ratings
API usage data8.94 Ratings00 Ratings
API user onboarding9.03 Ratings00 Ratings
API versioning8.94 Ratings00 Ratings
Usage billing and payments5.23 Ratings00 Ratings
API monitoring and logging9.84 Ratings00 Ratings
Best Alternatives
Azure API ManagementWSO2 Enterprise Service Bus
Small Businesses
NGINX
NGINX
Score 9.1 out of 10

No answers on this topic

Medium-sized Companies
NGINX
NGINX
Score 9.1 out of 10
Anypoint Platform
Anypoint Platform
Score 8.1 out of 10
Enterprises
NGINX
NGINX
Score 9.1 out of 10
Anypoint Platform
Anypoint Platform
Score 8.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Azure API ManagementWSO2 Enterprise Service Bus
Likelihood to Recommend
8.0
(4 ratings)
7.5
(5 ratings)
Usability
-
(0 ratings)
6.0
(1 ratings)
Availability
-
(0 ratings)
2.0
(1 ratings)
Performance
-
(0 ratings)
6.0
(1 ratings)
Support Rating
-
(0 ratings)
7.0
(1 ratings)
Configurability
-
(0 ratings)
5.0
(1 ratings)
Product Scalability
-
(0 ratings)
10.0
(1 ratings)
User Testimonials
Azure API ManagementWSO2 Enterprise Service Bus
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
WSO2 ESB is an awesome product for companies looking to venture into the world of SOA with an ESB. They have a lot of other products too that can work really well with their carbon infrastructure. The interface is simple for deploying and managing proxy services. You can also write custom modules within the ESB using Java with IDE like Eclipse
Read full review
Pros
Microsoft
  • Easy commissioning of APIs.
  • Great policies to control access.
  • Easy mock services for testing.
Read full review
WSO2
  • One of the basic requirement of an ESB product is that it should be able to support transformation. WSO2 ESB provides support of XSLT, so you can transform your request to whatever format. Moreover, transformations like converting your xml payload into JSON and JSON payload to XML are out of the box available.
  • WSO2 ESB provides a scheduler feature, by which you can configure your own scheduler to call a proxy service at a particular time of day or or initiate sequence.
  • WSO2 ESB provides excellent error handling techniques, WSO2 ESB provides detailed error handling scenarios to tackle all the situations. WSO2 ESB also provides custom error handling by which you can make your own custom error message before sending it back to client.
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
  • While it's easy to configure for a quick start, it is not so easy to deploy by yourself in a complex production scenario.
  • Not very stable for production usage, we encountered several trivial bugs that make us believe that this product is still not widely adopted.
  • Lack of a built in mechanism for auto-restart in case of an application server crash.
Read full review
Usability
Microsoft
No answers on this topic
WSO2
Compared to competitors the overall experience has been fine
Read full review
Reliability and Availability
Microsoft
No answers on this topic
WSO2
Lack of auto-restart built-in capabilities. In case of running out of memory there are no built-in methods to recover from a crash, just for example, Oracle WebLogic Node Manager.
Read full review
Performance
Microsoft
No answers on this topic
WSO2
The product is performing well and consuming few resources
Read full review
Support Rating
Microsoft
No answers on this topic
WSO2
Our experience with the WSO2 support has beent satisfactory
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
It's the only one truly open source and free.
Read full review
Scalability
Microsoft
No answers on this topic
WSO2
Adding a server node is really straightforward, there are just few point in the configuration files.
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
  • Very well documented tutorials and case studies makes it easy to learn.
  • It has a really supportive community
  • It is fast and it can easily handle 300 tps of average use on a VM with 4Gig RAM
Read full review
ScreenShots