Amazon API Gateway vs. Apigee Edge

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Amazon API Gateway
Score 8.2 out of 10
N/A
AWS 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
Apigee Edge
Score 7.8 out of 10
N/A
Apigee Edge is an API management platform now owned and offered by Google, since Google acquired Apigee in 2016.N/A
Pricing
Amazon API GatewayApigee Edge
Editions & Modules
Past 300 Million
$0.90
Per Million
First 300 Million
$1.00
Per Million
No answers on this topic
Offerings
Pricing Offerings
Amazon API GatewayApigee Edge
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
Amazon API GatewayApigee Edge
Considered Both Products
Amazon API Gateway
Chose Amazon API Gateway
Our primary architecture is AWS, so we selected [Amazon] API Gateway as our gateway solution. While Apigee and SwaggerHub provide great solutions for service orchestration, [Amazon] API Gateway provided the best integrations with our web services which were mostly running …
Chose Amazon API Gateway
I feel there is no competition to Amazon API Gateway when it comes to evaluating the cost and ease of use.
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 …
Apigee Edge
Chose Apigee Edge
Amazon API's gateway does not have easy to set up policies and exception handling. It does not have a tracking mechanism. However, it is better to use AWS API's gateway if you have tight integration with AWS tools.
Top Pros
Top Cons
Features
Amazon API GatewayApigee Edge
API Management
Comparison of API Management features of Product A and Product B
Amazon API Gateway
7.8
13 Ratings
7% below category average
Apigee Edge
9.4
7 Ratings
12% above category average
API access control6.512 Ratings9.07 Ratings
Rate limits and usage policies7.012 Ratings9.07 Ratings
API usage data8.212 Ratings9.07 Ratings
API user onboarding8.212 Ratings9.97 Ratings
API versioning9.212 Ratings9.97 Ratings
Usage billing and payments7.711 Ratings9.06 Ratings
API monitoring and logging7.513 Ratings9.97 Ratings
Best Alternatives
Amazon API GatewayApigee Edge
Small Businesses
NGINX
NGINX
Score 9.1 out of 10
NGINX
NGINX
Score 9.1 out of 10
Medium-sized Companies
NGINX
NGINX
Score 9.1 out of 10
NGINX
NGINX
Score 9.1 out of 10
Enterprises
NGINX
NGINX
Score 9.1 out of 10
NGINX
NGINX
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Amazon API GatewayApigee Edge
Likelihood to Recommend
8.0
(13 ratings)
9.0
(7 ratings)
Likelihood to Renew
-
(0 ratings)
9.0
(1 ratings)
Usability
-
(0 ratings)
9.0
(1 ratings)
Support Rating
10.0
(1 ratings)
6.0
(1 ratings)
User Testimonials
Amazon API GatewayApigee Edge
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.
Read full review
Google
Few scenarios 1. For viewing API analytics, I think it is best in the market 2. For earning money via API monetization 3. Securing API 4. Onboarding legacy APIs to provide modern REST endpoints
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.
Read full review
Google
  • Better exception handling with the Raise exception policies help to monitor the flow by setting up the flow conditions.
  • Easy development of a Proxy and APIs with much less tutoring and helps make getting started for new users easy.
  • Very good documentation and blog with details of most common failures and error handling.
  • A very very easy to use console.
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.
Read full review
Google
  • Only one user can be active in a proxy at a time
  • No version control
  • Prohibited from using JSON.stringify on Apigee objects (tokens)
  • Debugging is difficult
  • Unable to rename or delete policies without bumping revision
  • Why would anyone give a js policy one name, display name something else, and script a different name?
  • 'Trace' limited to only 20 transactions
  • UI allows users to add target servers, but users must utilize the api to turn on SSL.
  • I'm sure there's more, they just aren't coming to mind right now.
  • Apigee forgets (expires?) your password at random intervals without notice. Every few weeks, or days, sometimes even three times in one day, I'll attempt to login to Apigee and my password will be 'wrong'. I've reset my password and Apigee still claims it's wrong. I've had to reset my password three times before it finally let me log back in.
Read full review
Likelihood to Renew
Amazon AWS
No answers on this topic
Google
I am not the one deciding whether to use apigee or not really. But personally, I would recommend the use of it as developing APIs on it is easy. And as a mediator between backend servers, we could easily modify request and responses in it without touching any backend code while having a centralize gateway to access our backend APIs too.
Read full review
Usability
Amazon AWS
No answers on this topic
Google
Support has helped us to resolved all the queries and community support was also good.
Read full review
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.
Read full review
Google
Quite hard to get support, at least on the coding side, when we encounter blockers. But general concerns, they would schedule a call to you for them to get a whole picture of your concern. Albeit in my experience, bad really as they haven't replied about the progress, but otherwise seems to have been fixed.
Read full review
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.
Read full review
Google
Apigee is the best in the market in terms of API Analytics Apigee is having wonderful Documentation with short videos Security is a major concern and Apigee provides an easily configurable policy to secure API Quota and rate-limit is again very easy to configure on every API basis It provides various policies to transform the response from one form to another form e.g. JSON to XML or XML to JSON
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.
Read full review
Google
  • As a public entity it is hard to say how much ROI we can have. We have yet to create a billing and ROI plan. We are thinking of other ways to create ROI, possibly through data/service barter.
Read full review
ScreenShots