Back To the Basics - Service Mesh Fundamentals
summary
Explains that replacing Envoy sidecars with proxyless gRPC embeds an XDS client in the gRPC library, consumes the same XDS control plane config (listeners, routes, clusters, endpoints), and builds a per‑RPC LB tree with locality, weights and retries. Claims measurable wins: one fewer network hop, lower CPU and latency, higher QPS, and no control‑plane change (Traffic Director compatible). Limits: only for gRPC workloads and the library becomes part of the app lifecycle. Demo and open‑source implementation exist.
AI-written summary · about
chapters (14)
- 0:00Service mesh fundamentals
- 1:05Microservices and service mesh
- 3:14Sidecar proxies evolution
- 5:03Proxies with XDS
- 6:25Proxyless mesh with gRPC
- 8:50Bootstrapping gRPC for XDS
- 10:16gRPC proxyless advantages
- 13:28XDS protocol deep dive
- 18:12XDS resolution in gRPC
- 20:25Integrating XDS with gRPC
- 23:42gRPC service mesh features
- 25:29Control and management planes
- 26:54Demo and open-source
- 27:56Q&A on filters
related talks
16mxDS in gRPC for Service Mesh
17mBuilding a gRPC Proxyless World: How Reddit Scaled Resilience...
29mxds-relay: Performance initiatives for control plane management
36mReplacing NGINX with Envoy in a Traffic Control System
22mService Mesh in Kubernetes: It’s Not That Easy
30mIntroduction to Service Mesh for DevOps
21mProduction-Ready gRPC: How Service Meshes Simplify Security, Routing, and Observability
32mOne Size Doesn’t Fit All: Adding Org-Specific Gateway API Extensions with Envoy Gateway