Skip to main content

Kong

Kong is an Application Programming Interface (API) management and connectivity platform (API gateway and service mesh) that provides traffic control, security, and observability for microservices and APIs across hybrid and multi-cloud environments.

  • API gateway for routing, load balancing, authentication, and rate limiting (API management)
  • Service connectivity and discovery layer for microservices, including north-south and east-west traffic (service mesh / service connectivity)
  • Plugin-based policy enforcement for security, traffic control, and transformation (security / traffic management)
  • Deployment across Kubernetes, VMS, on-premises (on-prem), and cloud environments (infrastructure / hybrid and multi-cloud)
  • Control plane and developer-focused tooling for API lifecycle, governance, and observability (API lifecycle management / observability)

More About Kong

Kong is an API management and service connectivity platform (API gateway and service mesh) designed to manage, secure, and observe API and microservice traffic across heterogeneous infrastructures, including Kubernetes clusters, virtual machines, data centers, and public clouds. It operates as a programmable data plane for north-south and east-west traffic, giving platform and network teams a consistent way to control and monitor communication between clients, APIs, and backend services.

The platform’s core capabilities include request routing, load balancing, authentication and authorization (identity and access), rate limiting, request and response transformation, and observability (logging and metrics). Kong uses a plugin-based architecture (extensibility) that allows teams to enable or disable policies and behaviors on a per-service, per-route, or global basis. Plugins are available for security controls, traffic policies, data transformation, observability, and integrations with external identity providers and monitoring systems.

In enterprise environments, Kong is deployed as a high-performance API gateway (API management) in front of Representational State Transfer (REST), gRPC, and other HTTP-based services, and as a connectivity layer for microservices in containerized or hybrid environments. It can run in Kubernetes as ingress or as part of a broader service connectivity architecture, and it can also be deployed on virtual machines or bare metal. This flexibility enables consistent control over traffic flows across hybrid and multi-cloud topologies, where services and clients span multiple platforms and networks.

Kong provides a control plane (platform management) that manages configurations and policies for its data plane proxies. This architecture allows centralized configuration and governance while distributing traffic handling close to services. The platform exposes APIs and configuration interfaces that fit into Infrastructure-as-Code (IaC) workflows and Continuous Integration and Continuous Deployment (CI/CD) pipelines (infrastructure automation), enabling version-controlled policy changes and repeatable deployments. Kong’s support for mutual Transport Layer Security (TLS), JWT, OAuth2, and other authentication methods (security and identity) allows integration with enterprise identity and access management systems.

From a directory and taxonomy perspective, Kong fits into API management, API gateway, and service mesh / service connectivity categories. It is relevant to teams responsible for platform engineering, network engineering, and Security Operations (SecOps) who require standardized traffic management, policy enforcement, and observability across diverse runtime environments. Its extensible plugin model and support for multiple deployment patterns position it as a general-purpose connectivity layer that can integrate with monitoring, logging, and security tooling already present in enterprise stacks.

Mentions