What users are saying about
67 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.6 out of 100
12 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 5.7 out of 100

Likelihood to Recommend

Azure API Management

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.
Gordon Lo | TrustRadius Reviewer

WSO2 API Manager

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?
Anonymous | TrustRadius Reviewer

Feature Rating Comparison

API Management

Azure API Management
8.4
WSO2 API Manager
5.1
API access control
Azure API Management
9.0
WSO2 API Manager
8.0
Rate limits and usage policies
Azure API Management
7.4
WSO2 API Manager
8.0
API usage data
Azure API Management
9.0
WSO2 API Manager
1.0
API user onboarding
Azure API Management
9.0
WSO2 API Manager
4.0
API versioning
Azure API Management
8.4
WSO2 API Manager
9.0
Usage billing and payments
Azure API Management
7.0
WSO2 API Manager
5.0
API monitoring and logging
Azure API Management
9.0
WSO2 API Manager
1.0

Pros

Azure API Management

  • Selective data exposure as it exposes a set of data allowed by the owner by applying authentication and usage limits.
  • It will help us to keep all our APIs behind a single static IP and protect them with a set of keys.
  • Integration and deployment of various APIs are so simple to manage by Azure so that makes our work a lot easier.
aniket tiwari | TrustRadius Reviewer

WSO2 API Manager

  • Nice API store-front capability
  • Management of users and permissions
Anonymous | TrustRadius Reviewer

Cons

Azure API Management

  • We cannot automate the network infrastructure easily. At least we had issues with creating end to end APIM using Terraform.
Anonymous | TrustRadius Reviewer

WSO2 API Manager

  • Installation of this product is a hell. You need to be an expert to get this running together with WSO2 Analytics. It uses a really confusing method of "port + 1" to connect extra products. I guess this was meant to provide a handy way to add new WSO2 products. In reality you'll need to scroll through numerous config files to set this straight. If you use this out of the box, everything will work all right. But the moment you add SSL certificates, DNS names and you'll need special ports to configure your firewall, this product becomes unmaintainable.
  • The "Store" provides a nice way to group API's. However, the "Publisher" does not... if you have more than 30 API's searching for API's becomes really annoying.
  • The number of configs in this product is huge. As a developer myself, I've never seen (and definitely never created) a product that needed that much config files. Installation and maintenance of products should be stupidly simple, since no developer nor infrastructure person wants to learn something that "just" needs to be a tool.. opposed to being a whole new area of expertise. After using WSO2 API Manager for a while, we wanted to change the admin password... this should be simple enough, like just change the password in "Carbon." But nope. The whole WSO2 environment crashed. We just gave up. Too dangerous.
  • Why so many different "products"? Publisher, Store, Carbon, and numerous hidden interfaces. Analytics, ESB whatever... No wonder there are so many config files and port issues. Make it simple!!!
Anonymous | TrustRadius Reviewer

Alternatives Considered

Azure API Management

It’s a great tool, and so easy to seamlessly connect into your current Azure world that it’s hard not to look at it or even test the waters with it. It’s priced well, and is feature-rich enough to accomplish most tasks. I think the ease of having everything together and the ability to link so many different services under a subscription is the magic of Azure, and it’s hard not to make good use of that.
Anonymous | TrustRadius Reviewer

WSO2 API Manager

IBM API Manager is a better enterprise wide tool.
Anonymous | TrustRadius Reviewer

Return on Investment

Azure API Management

  • We can always think of positive ROI impact on business
  • It helps to easily facilitate the design, deployment, and maintenance of our APIs
Anonymous | TrustRadius Reviewer

WSO2 API Manager

  • 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.
Anonymous | TrustRadius Reviewer

Pricing Details

Azure API Management

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

WSO2 API Manager

General

Free Trial
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
No

Rating Summary

Likelihood to Recommend

Azure API Management
9.2
WSO2 API Manager
5.0

Add comparison