Amazon API Gateway vs Apigility vs Kong

Need advice about which tool to choose?Ask the StackShare community!

Amazon API Gateway

1.4K
1K
+ 1
45
Apigility

38
105
+ 1
2
Kong

629
1.5K
+ 1
139

Amazon API Gateway vs Apigility vs Kong: What are the differences?

  1. Integration Level: Amazon API Gateway is more tightly integrated with AWS services, providing seamless integration with Lambda functions, DynamoDB, and other AWS resources. Apigility, on the other hand, is more framework-agnostic and can be used with various PHP frameworks. Kong offers a flexible and platform-agnostic solution, allowing integration with any backend service or API.

  2. API Monitoring and Analytics: Amazon API Gateway and Kong offer built-in monitoring and analytics capabilities, providing detailed insights into API usage, performance, and errors. Apigility, while it offers logging and monitoring features, may require additional tooling for in-depth analytics and monitoring.

  3. Authentication and Authorization: Amazon API Gateway provides robust authentication and authorization mechanisms, including AWS IAM roles and policies. Apigility offers authentication plugins for standard protocols like OAuth, JWT, and basic authentication. Kong excels in its support for various authentication plugins, allowing easy integration with OAuth, JWT, Key authentication, etc.

  4. Deployment Flexibility: Amazon API Gateway is fully managed by AWS, offering ease of deployment and scaling. Apigility can be deployed on any PHP server, providing flexibility in deployment environments. Kong, being open-source, gives users the freedom to deploy it on-premises, in the cloud, or in a hybrid environment.

  5. API Rate Limiting and Throttling: Amazon API Gateway and Kong provide rate limiting and throttling controls out of the box, allowing users to manage API traffic effectively. Apigility, while it supports rate limiting, may require additional configuration or plugins for advanced throttling capabilities.

  6. Community Support and Ecosystem: Apigility has a strong community support system and a variety of plugins and modules available, making it easier for developers to extend and customize their APIs. Amazon API Gateway benefits from the vast AWS ecosystem, providing seamless integration with various AWS services. Kong, being open-source, has a vibrant community contributing plugins, integrations, and resources to enhance its capabilities.

In Summary, Amazon API Gateway, Apigility, and Kong offer unique strengths in integration, monitoring, deployment, authentication, and rate limiting for API management solutions.

Decisions about Amazon API Gateway, Apigility, and Kong
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 294.1K 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
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Amazon API Gateway
Pros of Apigility
Pros of Kong
  • 37
    AWS Integration
  • 7
    Websockets
  • 1
    Serverless
  • 1
    Follows Standards, Easy to Use, Design Patterns Used
  • 1
    Active dev community, full-featured, REST + RPC
  • 37
    Easy to maintain
  • 32
    Easy to install
  • 26
    Flexible
  • 21
    Great performance
  • 7
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Security
  • 2
    Has a good plugin infrastructure
  • 2
    Agnostic
  • 1
    Load balancing
  • 1
    Documentation is clear
  • 1
    Very customizable

Sign up to add or upvote prosMake informed product decisions

Cons of Amazon API Gateway
Cons of Apigility
Cons of Kong
  • 2
    No websocket broadcast
  • 1
    Less expensive
    Be the first to leave a con
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions