Proxies, Gateways, and Service Mesh. Why Are Words So Confusing?
Talkat Cloud Native University 2025 · on Tuesday, 2025-04-01· at 11:50· Level 0 | ICC Capital Hall | Room J·
summary
Bold claim: everything is a proxy—load balancers, API Gateways, Gateways, service meshes all sit between client and server and can read, modify, rate‑limit, terminate TLS, validate auth, or short‑circuit requests. Examples: Nginx/HAProxy act as L4/L7 proxies; Testcontainers uses a forward proxy pattern to tunnel to remote Docker; Gateway API is an API not the proxy itself. Service mesh equals an Envoy XDS control plane that enables live config, mTLS certificate rotation, retries, and policy enforcement at scale.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:45Proxies as traffic routers
- 4:31Proxy layers explained
- 9:04Forward vs reverse proxies
- 13:19Gateways for APIs
- 16:23Gateway API in Kubernetes
- 18:08Envoy and XDS config
- 20:39Service mesh control plane
- 22:23Summary
related talks
48mProxies, Gateways, and Service Mesh. Why Are Words so Confusing?
30mTo Mesh or not to Mesh
43mService Mesh and the future of networking
34mHow Many Proxies Do You Need?
32mAll the Proxies!
28mProxy Service: A New Network Traffic Abstraction in Kubernetes
18mHigh Performance Service Meshes with gRPC Proxyless
15mSimplify Kubernetes Connectivity