A Comprehensive Guide to API Gateways, K8s Gateways, and Service Meshes
summary
API gateways are essentially a reverse proxy with a policy layer (examples: Apache APISIX, Kong) that handles north–south functions like auth, rate limits and a 95/5 canary split example; Kubernetes gateways are the same gateway deployed in-cluster and configured via Ingress API or the new Gateway API (alpha) to avoid ad-hoc CRDs; service meshes handle east–west via sidecar proxies (Istio, Linkerd) or single-node eBPF-based proxies (Cilium) for lower latency and finer telemetry.
AI-written summary · about
chapters (10)
- 0:00API gateways and service meshes
- 3:15What is an API gateway
- 6:09Kubernetes gateways APIs
- 9:26API Gateway configs demo
- 13:37Gateway API vs Ingress API
- 15:43Service meshes and sidecars
- 18:56API gateways + service meshes
- 22:30API gateways vs service meshes
- 24:57Resources and reading
- 25:40Q&A
related talks
38mAPI Gateways & Service Mesh: What’s best for us
32mOne API To Rule Them All? What the Gateway API Means For Service Meshes
39mAPI Gateway to Service Mesh: Navigating a Changing Landscape
09mK8s API Gateway: Service Mesh Strategies for Scalable Solutions
40mThe Busy Platform Engineers Guide to API Gateways
26mSynchronous Communication Patterns: A journey from ESB to APIs [...]
33mFantastic API Gateways and Where to Find Them
55mAPI Gateways with Kong