description Kong Gateway Overview
Kong is a robust API Gateway designed to sit at the edge of a microservices architecture. It acts as a central control plane, managing traffic, security policies, and observability for dozens of backend services. It enforces rate limiting, handles authentication (JWT, OAuth), and provides necessary abstraction, making it crucial for large-scale, distributed systems that need governance.
help Kong Gateway FAQ
What problem does Kong Gateway solve in a microservices stack?
Kong Gateway sits in front of backend services and centralizes API traffic control. Teams use it for routing, authentication, rate limiting, logging, and observability instead of duplicating those features in every service.
Is Kong Gateway based on NGINX?
Kong Gateway is built on top of NGINX and OpenResty in its traditional architecture. That is why it is often chosen for high-throughput reverse proxy and API gateway use cases.
What plugins are common in Kong Gateway deployments?
Common Kong plugins include rate limiting, key authentication, JWT authentication, OAuth-related integrations, request transformation, and logging plugins. The plugin model is one of Kong's main selling points.
How is Kong Gateway different from Kubernetes Ingress?
A Kubernetes Ingress usually focuses on routing traffic into cluster services, while Kong adds API management features such as consumers, plugins, and policy enforcement. Kong can also run as a Kubernetes ingress controller when deployed that way.
explore Explore More
Similar to Kong Gateway
See all arrow_forward
Reviews & Comments
Write a Review
Be the first to review
Share your thoughts with the community and help others make better decisions.
