TrustRadius: an HG Insights company

Azure API Management vs. IBM DataPower Gateway

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Azure API Management

    Score8 out of 10
    N/AMicrosoft's Azure API Management supports creation of API.

    $0.04

    per 10,000 calls

    IBM DataPower Gateway

    Score8 out of 10
    N/AThe IBM DataPower Gateway is a security and integration platform.N/A
    Pricing
    Azure API ManagementIBM DataPower Gateway
    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 ManagementIBM DataPower Gateway
    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
    Features
    Azure API ManagementIBM DataPower Gateway
    API Management
    Comparison of API Management features of Azure API Management and IBM DataPower Gateway
    Feature
    Azure API Management
    8.0
    4 Ratings
    4% below category average
    IBM DataPower Gateway
    -
    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 ManagementIBM DataPower Gateway
    Small Businesses
    Amazon API Gateway
    Score8.2 out of 10
    No answers on this topic
    Medium-sized Companies
    Amazon API Gateway
    Score8.2 out of 10
    Mule ESB
    Score9 out of 10
    Enterprises
    OCI API Management
    Score8.2 out of 10
    Mule ESB
    Score9 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    Azure API ManagementIBM DataPower Gateway
    Likelihood to Recommend
    8.0
    (4 ratings)
    8.2
    (2 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    7.0
    (1 ratings)
    User Testimonials
    Azure API ManagementIBM DataPower Gateway
    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.
    Incentivized
    Read full review
    IBM
    WebSphere DataPower Gateway is really beneficial if you are trying to integrate two or more systems. It provides you with comfort and peace of mind by creating a DMZ zone for the services which are going out of the intranet to hit external clients APIs. It is greatly recommended if you have a very high volume service or API which is being used by a majority of clients because it has a dedicated physical box present which takes care of memory, CPU and all such stuff. So, all your transactions happen at wire-speed.
    Incentivized
    Read full review
    Pros
    Microsoft
    • Easy commissioning of APIs.
    • Great policies to control access.
    • Easy mock services for testing.
    Incentivized
    Read full review
    IBM
    • The most obvious thing that DataPower does exceptionally well is security. All the built-in supported security capabilities allow us to isolate most security tasks to DataPower and as a result "protect" down steam services/systems to have to deal with security.
    • DataPower is very good at protocol conversion and as it is usually used on the edge allows you to narrow down the protocols used between the companies public and private networks.
    • The appliance concept makes maintenance, recovery and, management so much simpler.
    Incentivized
    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.
    Incentivized
    Read full review
    IBM
    • The old interface is being really missed by our team as the new WebUI interface is not that intuitive or easy to work with. It takes a lot of time to load. There should be an inbuilt wizard for creating a Rest service as well like there is for an XML based service.
    • IBM support is very knowledgeable but it's not that easy to reach them. They don't release the fix patches very soon which also becomes a big issue in certain situations where critical projects are involved.
    • Lastly, DataPower has its steep learning curve and it requires time and effort on your end to gain full control and make the most of the advanced features which it offers. Finding the right resource in the market is not that easy.
    Incentivized
    Read full review
    Likelihood to Renew
    Microsoft
    No answers on this topic
    IBM
    Cost of the appliance
    Incentivized
    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.
    Incentivized
    Read full review
    IBM
    No answers on this topic
    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
    IBM
    • It has really taken our business to the next level. We have expanded and integrated with so many new vendors and for all those integrations DataPower is serving as our security gateway.
    • We don't have to depend on any other tool for doing the load balancing of the incoming requests as that is also taken care inside the WebSphere DataPower Gateway box itself, thereby distributing the load equally.
    • It has made our platform much more secure, uniform and robust to deal with any kind of incoming message format or threat as well due to its latest security mechanisms and huge processing power.
    Incentivized
    Read full review
    ScreenShots