gRPC Load Balancing

Client-side or proxy-based distribution of gRPC calls — options include pick-first, round-robin, and xDS-based policies for service mesh integration. Because gRPC uses persistent HTTP/2 connections, a naive TCP load balancer will route all requests from one client to the same backend. L7-aware load balancing (per-RPC, not per-connection) requires the load balancer or client to inspect HTTP/2 frames and distribute streams independently.