Proxies, Gateways, and Service Mesh. Why Are Words so Confusing?
summary
Bold claim: everything is a proxy or, if not, a VPN. Demonstrates by writing a tiny Rust proxy that listens on 8100 and forwards to 8000, then boots Nginx to prove real traffic flow with curl. Distinguishes load balancers, Kubernetes Ingress vs Gateway API, and API Gateways as proxies that enforce auth/rate limits. Explains Envoy (from Lyft) with Envoy + XDS control plane, Istio-style sidecar meshes with sidecar per instance, and alternatives: ambient mesh and eBPF replacements.
AI-written summary · about
chapters (9)
- 0:00Talk introduction
- 1:05What is a proxy
- 13:25Proxy types and examples
- 21:55Gateways vs proxies
- 26:50Kubernetes Ingress explained
- 31:08Envoy and service mesh
- 35:53Why service mesh
- 38:23Service mesh challenges
- 41:40Q&A session
related talks
23mProxies, Gateways, and Service Mesh. Why Are Words So Confusing?
34mHow Many Proxies Do You Need?
30mTo Mesh or not to Mesh
15mSimplify Kubernetes Connectivity
26mNetworking the Service Mesh Proxy: Where We Are, Where We’re Going
28mProxy Service: A New Network Traffic Abstraction in Kubernetes
33mTake Envoy Beyond a K8s Service Mesh - to Legacy Bare Metal & VMs + More
34mAsk Me Anything