Using a Service Mesh With gRPC
summary
gRPC requires HTTP/2 and works with common service meshes but the interaction depends on architecture: gateway, daemonset, sidecar, proxyless each changes where TLS, load balancing and observability live. L4 proxies only balance connections; L7 proxies can do per-RPC routing, which is why heavy gRPC traffic often prefers proxyless or a waypoint for per-RPC load balancing. Examples: Linkerd can upgrade HTTP1 to HTTP2, Istio mixes L4/L7, and Google Cloud Service Mesh (Traffic Director) supports proxyless pods in a single mesh.
AI-written summary · about
chapters (14)
- 0:00Service meshes and gRPC intro
- 1:47Service mesh architectures
- 3:15Sidecar proxy models
- 5:22Layer 4 vs Layer 7 proxies
- 6:49gRPC with service meshes
- 7:53Load balancing gRPC in meshes
- 9:22Proxy model trade-offs
- 10:25Proxyless gRPC deployments
- 11:48Q&A: HTTP/3 and mesh
- 13:57Q&A: HTTP/3 in GCP
- 15:21Q&A: gRPC versioning
- 16:44Q&A: Proxyless gRPC benefits
- 18:51Q&A: Sidecar vs proxyless
- 20:36Q&A: gRPC security
related talks
23mHow Proxyless gRPC Works in a Service Mesh
20mProxyless Service Mesh with gRPC
23mA Simplified Service Mesh With gRPC
33mgRPC For Microservices: Service-mesh and Observability
35mgRPC Load Balancing on Kubernetes - Jan Tattermusch, Google
24mgRPC Proxyless Service Mesh
43mWTF Do We Need a Service Mesh?
30mgRPC & Kubernetes