Amazon API Gateway vs. Kubernetes

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Amazon API Gateway
Score 8.3 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
Kubernetes
Score 9.0 out of 10
N/A
Kubernetes is an open-source container cluster manager.N/A
Pricing
Amazon API GatewayKubernetes
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 GatewayKubernetes
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 GatewayKubernetes
Considered Both Products
Amazon API Gateway
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.
Kubernetes

No answer on this topic

Top Pros
Top Cons
Features
Amazon API GatewayKubernetes
API Management
Comparison of API Management features of Product A and Product B
Amazon API Gateway
7.7
13 Ratings
8% below category average
Kubernetes
-
Ratings
API access control6.412 Ratings00 Ratings
Rate limits and usage policies7.012 Ratings00 Ratings
API usage data8.212 Ratings00 Ratings
API user onboarding8.212 Ratings00 Ratings
API versioning9.212 Ratings00 Ratings
Usage billing and payments7.611 Ratings00 Ratings
API monitoring and logging7.413 Ratings00 Ratings
Container Management
Comparison of Container Management features of Product A and Product B
Amazon API Gateway
-
Ratings
Kubernetes
8.3
3 Ratings
6% above category average
Security and Isolation00 Ratings8.73 Ratings
Container Orchestration00 Ratings9.23 Ratings
Cluster Management00 Ratings9.43 Ratings
Storage Management00 Ratings7.23 Ratings
Resource Allocation and Optimization00 Ratings7.63 Ratings
Discovery Tools00 Ratings8.13 Ratings
Update Rollouts and Rollbacks00 Ratings8.13 Ratings
Self-Healing and Recovery00 Ratings8.52 Ratings
Analytics, Monitoring, and Logging00 Ratings8.13 Ratings
Best Alternatives
Amazon API GatewayKubernetes
Small Businesses
NGINX
NGINX
Score 9.1 out of 10
Portainer
Portainer
Score 9.4 out of 10
Medium-sized Companies
NGINX
NGINX
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
Enterprises
NGINX
NGINX
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Amazon API GatewayKubernetes
Likelihood to Recommend
8.0
(13 ratings)
9.4
(18 ratings)
Usability
-
(0 ratings)
8.0
(2 ratings)
Support Rating
10.0
(1 ratings)
-
(0 ratings)
User Testimonials
Amazon API GatewayKubernetes
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
Kubernetes
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
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
Kubernetes
  • Complex cluster management can be done with simple commands with strong authentication and authorization schemes
  • Exhaustive documentation and open community smoothens the learning process
  • As a user a few concepts like pod, deployment and service are sufficient to go a long way
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
Kubernetes
  • Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
  • The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
  • Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
Read full review
Usability
Amazon AWS
No answers on this topic
Kubernetes
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
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
Kubernetes
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.
Read full review
Kubernetes
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
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
Kubernetes
  • Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
  • Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.
Read full review
ScreenShots