> For the complete documentation index, see [llms.txt](https://docs.imesh.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imesh.ai/imesh-api-gateway/concepts.md).

# Concepts

The Kubernetes community has started [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/), standardizing how north-south traffic is handled in Kubernetes clusters. The three primary goals of this standardization are: 

* Generalization of configuration to avoid vendor-locking, 
* Expressiveness for core traffic functionality (header-based routing, traffic weighting, etc.)
* Role-oriented design to improve self-service of API creation.

The idea is that in emerging startups or enterprises, DevOps or the platform team would own the creation of a Gateway to listen to external traffic, and developers would create Routes (like APIs) to map the traffic from the Gateway to their backend services in Kubernetes. 

<br>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXclGHcqz-AnX3Cn4iiUBoYhqGYb6cUf-J6M50LZYw-JDI1vwm3qGO0oLYBrgbGSiyoWLdJ2EMzTDhebVPs77CrcIUtx8127epMPlelQrEHr2v87nG3tjyhYi_QJ1ZsDCJXycRCVEjidzJbz1TC1Cwb8KvYL?key=TmnoeuMYwYPADPNdd3FkNg" alt=""><figcaption></figcaption></figure>

#### Key benefits of IMESH API Gateway

1. Fast, secure, and scalable traffic&#x20;
2. Rise in developer’s productivity with low-code API management solution
3. Implementation of multi-tenancy with RBAC of API management
4. Faster troubleshooting of production issues with real-time traffic insights.
5. Less hassle with integrations with built-in integration with Kubernetes-native platforms such as Prometheus, Grafana, Argo CD, and Istio service mesh
6. High flexibility to rip-and-replace ingress controllers as per convenience, as IMESH provides support for Istio and Envoy Gateway controllers.

<br>