How Proxyless gRPC Works in a Service Mesh
summary
gRPC implements an embedded xDS name resolver and an xDS client so applications can get service discovery, LB and routing directly from a control plane (examples: Envoy data plane and STO control plane). Configuration comes from a bootstrap file listing XDS servers and credentials; resources are Listener, Route, Cluster and Endpoint; gRPC builds a runtime load‑balancer tree that does per‑RPC routing with priority + weighted locality and health info, removing the sidecar hop.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:45What is a service mesh
- 2:30Sidecar proxy pattern
- 5:01Evolution to XDS with Envoy
- 6:25Proxyless gRPC
- 8:53XDS API structure
- 14:52Load balancing in XDS
- 18:06Q&A
related talks
20mProxyless Service Mesh with gRPC
23mA Simplified Service Mesh With gRPC
16mxDS in gRPC for Service Mesh
33mgRPC For Microservices: Service-mesh and Observability
46mProxyless Service Mesh for gRPC Java Services
22mUsing a Service Mesh With gRPC
25mAdapting Our XDS Control Plane for Proxyless gRPC
34mgRPC Proxyless Service Mesh with Security