Skip to content

StackOS Community Q&A • best-practice

How to evaluate and select an API gateway for microservices?

We're transitioning from a monolith to microservices and need an API gateway. Our requirements: - Handle 10K requests/second - Rate limiting and authentication - gRPC support - Kubernetes-native deployment - Low latency (<10ms added overhead) Options we're considering: Kong, Envoy, APISIX, AWS API Gateway. Any real-world comparisons?

Top Community Answer

We evaluated all four and went with Kong. Here's why, and where the others might be better: **Kong** - Pros: Plugin ecosystem (100+ plugins), Kong Ingress Controller for K8s, DB-less mode for low latency, Enterprise has good support - Cons: Configuration can be complex, Enterprise pricing is steep - Best for: Teams that want extensibility and a proven track record **Envoy** - Pros: Built for high performance (C++), excellent gRPC support, used by Google/Apple - Cons: Steep learning curve, needs a control plane (Istio/Contour) for full management - Best for: Teams with K8s expertise that need maximum performance **APISIX** - Pros: High performance (also C++/Lua), built-in dashboard, good China market support - Cons: Smaller community in English, fewer enterprise references - Best for: Cost-conscious teams comfortable with Apache projects **AWS API Gateway** - Pros: Zero infra management, native WAF integration - Cons: Vendor lock-in, 10ms+ latency overhead, limited gRPC (only HTTP/2 mapping), expensive at scale - Best for: Teams already all-in on AWS with simple routing needs Our choice: Kong in DB-less mode on K8s. We get 3-5ms overhead with 15+ plugins active.