gRPC on Web — Lessons & Roadmap
summary
grpc-web has five years of usage data since October 2018 and explains concrete tradeoffs: it relies on Envoy translation to convert grpc-web to gRPC, enforces server streaming only (no request/client streaming over HTTP/1.1 because an origin trial failed), and treats code size as a hard constraint (Google triggers an alert per extra 1 KB). Practical problems include the Closure Compiler dependency and poor protobuf-js UX/performance; roadmap items are WebTransport over QUIC for full‑duplex streaming and alignment of protobuf JS/node stacks.
AI-written summary · about
chapters (5)
- 0:00gRPC on Web intro
- 1:06Design goals and history
- 8:39Five years of lessons
- 16:26Future roadmap
- 24:20Q&A
