What users are saying about
93 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.7 out of 100
16 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

Feature Set Ratings

  • WSO2 API Manager ranks higher in 1 feature set: API Management

API Management

8.0

Azure API Management

80%
8.1

WSO2 API Manager

81%
WSO2 API Manager ranks higher in 4/7 features

API access control

8.7
87%
4 Ratings
9.2
92%
4 Ratings

Rate limits and usage policies

6.1
61%
4 Ratings
9.2
92%
4 Ratings

API usage data

8.7
87%
4 Ratings
6.7
67%
4 Ratings

API user onboarding

9.0
90%
3 Ratings
7.3
73%
4 Ratings

API versioning

8.7
87%
4 Ratings
9.0
90%
4 Ratings

Usage billing and payments

5.6
56%
3 Ratings
8.3
83%
4 Ratings

API monitoring and logging

9.4
94%
4 Ratings
7.1
71%
4 Ratings

Attribute Ratings

  • WSO2 API Manager is rated higher in 1 area: Likelihood to Recommend

Likelihood to Recommend

8.3

Azure API Management

83%
4 Ratings
8.7

WSO2 API Manager

87%
4 Ratings

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

Pricing Details

Azure API Management

Starting Price

$0.042 per 10,000 calls

Editions & Modules

Azure API Management editions and modules pricing
EditionModules
Consumption0.042 per 10,000 calls1
Developer$48.042
Basic$147.173
Standard$686.724
Premium$2,795.175
IsolatedTBA6

Footnotes

  1. Lightweight and serverless version of API Management service, billed per execution
  2. per month Non-production use cases and evaluations
  3. per month Entry-level production use cases
  4. per month Medium-volume production use cases
  5. per month High-volume or enterprise production use cases
  6. per month Enterprise production use cases requiring high degree of isolation

Offerings

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services

Entry-level set up fee?

No setup fee

Additional Details

WSO2 API Manager

Starting Price

Editions & Modules

WSO2 API Manager editions and modules pricing
EditionModules

Footnotes

    Offerings

    Free Trial
    Free/Freemium Version
    Premium Consulting/Integration Services

    Entry-level set up fee?

    No setup fee

    Additional Details

    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

    Add comparison