TrustRadius: an HG Insights company

Amazon API Gateway vs. AWS Lambda vs. Azure API Management

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Amazon API Gateway

    Score7.2 out of 10
    N/AAWS offers the Amazon API Gateway supports the creation and publication of an API for web applications, as well as its monitoring and maintenance. The Amazon API Gateway is able to support thousands of API calls concurrently and provides traffic management, as well as monitoring and access control.

    $0.90

    Per Million

    AWS Lambda

    Score8.3 out of 10
    N/AAWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.

    $NaN

    Per 1 ms

    Azure API Management

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

    $0.04

    per 10,000 calls

    Pricing
    Amazon API GatewayAWS LambdaAzure API Management
    Editions & Modules
    Past 300 Million
    $0.90
    Per Million
    First 300 Million
    $1.00
    Per Million
    128 MB
    $0.0000000021
    Per 1 ms
    1024 MB
    $0.0000000167
    Per 1 ms
    10240 MB
    $0.0000001667
    Per 1 ms
    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
    Offerings
    Pricing Offerings
    Amazon API GatewayAWS LambdaAzure API Management
    Free Trial
    NoNoNo
    Free/Freemium Version
    NoNoNo
    Premium Consulting/Integration Services
    NoNoNo
    Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
    Additional Details———
    More Pricing Information
    Community Pulse
    Amazon API GatewayAWS LambdaAzure API Management
    Considered Multiple Products
    Amazon AWS
    Chose Amazon API Gateway
    When we tested Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up …
    Incentivized
    Chose Amazon API Gateway
    Our organization uses AWS infrastructure for many projects across different business units so we choose Amazon API Gateway for initial web services development. After exploring all features especially integration with other Amazon services like Lamda and Cloud watch we chose to …
    Incentivized
    Chose Amazon API Gateway
    Compared to other solutions, Azure is much easier to use and setup, but probably for hybrid solution Talend API in the cloud is the best solution and Talend API can take advantage of Amazon API Gateway, thus all this hard work is done by other software solution. Additionally, …
    Incentivized
    Chose Amazon API Gateway
    As AWS API comes with more security and API key authentication functions, it's easy for the organization to handle the various customers based with different level of permission. And also very easy comparable to others for tracking the API calls. Also, scalability and …
    Incentivized
    Chose Amazon API Gateway
    Since we have been using AWS products since the beginning, we did not think about using any competitors of API Gateway. It has great and strong integration with other AWS products.
    Incentivized
    Amazon AWS
    Chose AWS Lambda
    It's fine, it works as the others would have, except EC2. We are migrating back to EC2 for dedicated compute because we have scaled to a point where we have consistent traffic. The tradeoff of maintaining infrastructure in-house outweighs the benefits of moving quickly through …
    Incentivized
    Chose AWS Lambda
    AWS is great product and a close match our expectations. It is close to Azure in function but more feature rich with API and support documents. From my experience, it is cheaper compared with our competitors and provides better interface. Overall our dev engineers prefer AWS …
    Incentivized
    Chose AWS Lambda
    These are all AWS sister products, so I wouldn't say they are competitors but tools in the same box. They all work quite well together and I would say combined they are greater than the sum of their parts. Cloudformation (and SAM) templates make tying them together pretty …
    Incentivized
    Chose AWS Lambda
    I don't know nor have used any other product that really competes with AWS Lambda. I would think Microsoft would have a product that completes with AWS Lambda but I have never used it.
    Incentivized
    Chose AWS Lambda
    All were part of the stack we used. Integration was seamless and have not had any load issues.
    Incentivized
    Microsoft
    Chose Azure API Management
    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.
    Incentivized
    Chose 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 …
    Incentivized
    Key User Insights
    Would buy again
    89%
    Would buy again
    8 Answers
    100%
    Would buy again
    24 Answers
    No answers on this topic
    Delivers good value for the price
    89%
    Delivers good value for the price
    8 Answers
    96%
    Delivers good value for the price
    22 Answers
    No answers on this topic
    Happy with the feature set
    89%
    Happy with the feature set
    8 Answers
    100%
    Happy with the feature set
    24 Answers
    No answers on this topic
    Lived up to sales and marketing promises
    89%
    Lived up to sales and marketing promises
    8 Answers
    100%
    Lived up to sales and marketing promises
    18 Answers
    No answers on this topic
    Implementation went as expected
    89%
    Implementation went as expected
    8 Answers
    100%
    Implementation went as expected
    21 Answers
    No answers on this topic
    Features
    Amazon API GatewayAWS LambdaAzure API Management
    API Management
    Comparison of API Management features of Amazon API Gateway and AWS Lambda and Azure API Management
    Feature
    Amazon API Gateway
    9.1
    14 Ratings
    8% above category average
    AWS Lambda
    -
    Ratings
    Azure API Management
    8.0
    4 Ratings
    5% below category average
    API access control9.013 Ratings00 Ratings8.94 Ratings
    Rate limits and usage policies10.013 Ratings00 Ratings5.44 Ratings
    API usage data8.013 Ratings00 Ratings8.94 Ratings
    API user onboarding8.013 Ratings00 Ratings9.03 Ratings
    API versioning9.013 Ratings00 Ratings8.94 Ratings
    Usage billing and payments10.012 Ratings00 Ratings5.23 Ratings
    API monitoring and logging10.014 Ratings00 Ratings9.84 Ratings
    Access Control and Security
    Comparison of Access Control and Security features of Amazon API Gateway and AWS Lambda and Azure API Management
    Feature
    Amazon API Gateway
    -
    Ratings
    AWS Lambda
    8.8
    7 Ratings
    4% above category average
    Azure API Management
    -
    Ratings
    Multiple Access Permission Levels (Create, Read, Delete)00 Ratings8.57 Ratings00 Ratings
    Single Sign-On (SSO)00 Ratings9.03 Ratings00 Ratings
    Reporting & Analytics
    Comparison of Reporting & Analytics features of Amazon API Gateway and AWS Lambda and Azure API Management
    Feature
    Amazon API Gateway
    -
    Ratings
    AWS Lambda
    4.9
    6 Ratings
    29% below category average
    Azure API Management
    -
    Ratings
    Dashboards00 Ratings5.46 Ratings00 Ratings
    Standard reports00 Ratings5.05 Ratings00 Ratings
    Custom reports00 Ratings4.35 Ratings00 Ratings
    Function as a Service (FaaS)
    Comparison of Function as a Service (FaaS) features of Amazon API Gateway and AWS Lambda and Azure API Management
    Feature
    Amazon API Gateway
    -
    Ratings
    AWS Lambda
    8.8
    7 Ratings
    5% above category average
    Azure API Management
    -
    Ratings
    Programming Language Diversity00 Ratings9.07 Ratings00 Ratings
    Runtime API Authoring00 Ratings8.07 Ratings00 Ratings
    Function/Database Integration00 Ratings9.07 Ratings00 Ratings
    DevOps Stack Integration00 Ratings9.27 Ratings00 Ratings
    Best Alternatives
    Amazon API GatewayAWS LambdaAzure API Management
    Small Businesses
    No answers on this topic
    IBM Cloud Functions
    Score6.5 out of 10
    Amazon API Gateway
    Score7.2 out of 10
    Medium-sized Companies
    Azure API Management
    Score9.1 out of 10
    IBM Cloud Functions
    Score6.5 out of 10
    Amazon API Gateway
    Score7.2 out of 10
    Enterprises
    OCI API Management
    Score7.9 out of 10
    IBM Cloud Functions
    Score6.5 out of 10
    OCI API Management
    Score7.9 out of 10
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    Amazon API GatewayAWS LambdaAzure API Management
    Likelihood to Recommend
    8.0
    (14 ratings)
    7.5
    (52 ratings)
    8.0
    (4 ratings)
    Usability
    9.0
    (1 ratings)
    8.3
    (17 ratings)
    -
    (0 ratings)
    Support Rating
    10.0
    (1 ratings)
    8.7
    (20 ratings)
    -
    (0 ratings)
    User Testimonials
    Amazon API GatewayAWS LambdaAzure API Management
    Likelihood to Recommend
    Amazon AWS
    Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.
    Incentivized
    Read full review
    Amazon AWS
    Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.
    Incentivized
    Read full review
    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
    Pros
    Amazon AWS
    • API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway.
    • API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting).
    • API Gateway's pricing can be very attractive for services that are accessed infrequently.
    Incentivized
    Read full review
    Amazon AWS
    • No provisioning required - we don't have to pay anything upfront
    • Serverless deployment - it gets executed only when request comes and we pay only for the time the request is getting executed
    • Integrates well with AWS CloudWatch triggers so it is easy to setup scheduled tasks like cron jobs
    Incentivized
    Read full review
    Microsoft
    • Easy commissioning of APIs.
    • Great policies to control access.
    • Easy mock services for testing.
    Incentivized
    Read full review
    Cons
    Amazon AWS
    • Client certificates are troublesome when trying to attach them to API GW stages.
    • Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB.
    • Creating internal/private APIs, particularly with custom domains, can be unintuitive.
    Incentivized
    Read full review
    Amazon AWS
    • Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
    • For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
    • Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
    • Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
    Incentivized
    Read full review
    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
    Usability
    Amazon AWS
    It is a great product very reliable and stable for connecting various aws services like we connected with lambda function and it is working very well, never faced any issue after the setup. It also saves out lots of money as well as time after we implemented the automatic ec2 server recovery system
    Incentivized
    Read full review
    Amazon AWS
    I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.
    Incentivized
    Read full review
    Microsoft
    No answers on this topic
    Support Rating
    Amazon AWS
    We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.
    Incentivized
    Read full review
    Amazon AWS
    Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.
    Incentivized
    Read full review
    Microsoft
    No answers on this topic
    Alternatives Considered
    Amazon AWS
    When we tested Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.
    Incentivized
    Read full review
    Amazon AWS
    AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions
    Incentivized
    Read full review
    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
    Return on Investment
    Amazon AWS
    • ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues.
    • For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical.
    • Service is easy to set up authorization and it is easy to manage.
    Incentivized
    Read full review
    Amazon AWS
    • Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
    • Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
    • Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.
    Incentivized
    Read full review
    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
    ScreenShots