xDS in gRPC for Service Mesh
summary
gRPC now embeds a data plane so services can skip sidecar proxies and speak xDS to a control plane directly. It uses an xds resolver and a small bootstrap file to locate the control plane, enabling service discovery, load balancing, route matching and traffic splitting today. Limitations include feature gaps versus Envoy, limited language support, and ongoing work for mTLS, timeouts/circuit breaking and broader control plane compatibility (Traffic Director supported now).
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:15gRPC and microservices
- 2:58gRPC and service mesh
- 5:09Limitations of sidecar proxies
- 7:40What is xDS
- 8:56xDS and gRPC
- 10:40Limitations
- 12:14Current Status
- 13:23Control Plane
- 15:01Resources
related talks
20mProxyless Service Mesh with gRPC
23mxDS Support in gRPC
23mHow Proxyless gRPC Works in a Service Mesh
23mA Simplified Service Mesh With gRPC
35mBack To the Basics - Service Mesh Fundamentals
33mgRPC For Microservices: Service-mesh and Observability
25mAdapting Our XDS Control Plane for Proxyless gRPC
34mgRPC Proxyless Service Mesh with Security