Amazon API Gateway vs Apigility vs Kong

Amazon API Gateway

982
723
+ 1
37
Apigility

35
90
+ 1
2
Kong

382
898
+ 1
121
Decisions about Amazon API Gateway, Apigility, and Kong
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 73.4K views

Istio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn-keyIstio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn key solution with Rancher whereas Kong completely lacks here. Traffic distribution in Istio can be done via canary, a/b, shadowing, HTTP headers, ACL, whitelist whereas in Kong it's limited to canary, ACL, blue-green, proxy caching. Istio has amazing community support which is visible via Github stars or releases when comparing both.

See more
Pros of Amazon API Gateway
Pros of Apigility
Pros of Kong

Sign up to add or upvote prosMake informed product decisions

Cons of Amazon API Gateway
Cons of Apigility
Cons of Kong
    No cons available
      No cons available

      Sign up to add or upvote consMake informed product decisions