gRPC For Microservices: Service-mesh and Observability
summary
gRPC is extended to run a proxyless (proximal) service mesh using xDS so gRPC clients and servers enforce routing, LB and mTLS without Envoy sidecars; Fortio benchmarks on GKE (3 e2-standard-16 nodes) show 6–16× latency improvement at 64 connections versus Envoy while keeping advanced traffic policies. xDS uses LDS/RDS/CDS/EDS for routing and endpoints; the Istio agent still runs but costs <0.1% CPU, 25 MB memory for the agent compared with Envoy. Observability uses interceptors, exporters (Stackdriver), and the grpc-gcp-observability Java artifact for logs, metrics and traces (logging in private preview; metrics/traces coming soon).
AI-written summary · about
chapters (12)
- 0:00Start
- 3:41Intro to gRPC: Protobuf
- 4:38Intro to gRPC: In a nutshell...
- 8:31RPC & Service Mesh
- 10:06GRPC & Proxyless Service Mesh
- 15:15Traffic Management in the Service Mesh
- 18:03Service Mesh with Security
- 26:05GRPC Observability aka 011y
- 28:21GRPC Observability with Java
- 29:36GRPC Observability GCP Config
- 31:29GRPC Observability Logging Preview
- 32:28GRPC Observability: Metrics
related talks
23mA Simplified Service Mesh With gRPC
23mHow Proxyless gRPC Works in a Service Mesh
20mProxyless Service Mesh with gRPC
16mxDS in gRPC for Service Mesh
22mUsing a Service Mesh With gRPC
34mgRPC Proxyless Service Mesh with Security
25mAdapting Our XDS Control Plane for Proxyless gRPC
26mFeature Work In GRPC; XDS And Not