A Simplified Service Mesh With gRPC
summary
gRPC adds a proxy-less gRPC model that uses xDS to push listeners, routes, clusters and endpoints into the client so services do discovery and load balancing without sidecar proxies. gRPC 1.30 ships xDS for service discovery and endpoint LB, with route matching and cluster splitting in progress and a v2→v3 migration planned. Demo uses Google Traffic Director and a hello‑world GCE backend across two regions to show fast cross‑region failover. Configuration comes from an xDS bootstrap file. Downsides: fewer ecosystem filters than Envoy and requires upgrading clients.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:24gRPC
- 1:05Service Mesh
- 1:59Common Problems
- 2:24Where does gRPC stand
- 3:42How gRPC is deployed
- 4:48Service Mesh Integration
- 5:38Which Service Mesh
- 6:57xts APIs
- 7:33xts API overview
- 10:20gRPC xts implementation
- 12:38Enabling xts
- 14:24Advantages
- 16:15Downsides
- 17:53Where are we
- 18:44Demo
- 22:10End
related talks
20mProxyless Service Mesh with gRPC
23mHow Proxyless gRPC Works in a Service Mesh
33mgRPC For Microservices: Service-mesh and Observability
16mxDS in gRPC for Service Mesh
34mgRPC Proxyless Service Mesh with Security
25mAdapting Our XDS Control Plane for Proxyless gRPC
23mxDS Support in gRPC
17mBuilding a gRPC Proxyless World: How Reddit Scaled Resilience...