gRPC Web: It’s All About Communication
summary
A browser game demonstrates a real gRPC backend: a gateway exposes three gRPC APIs (fixtures, getTopScores, updateScore), JavaScript/TypeScript clients are auto-generated from proto files and called via grpc-web generated JS clients, and an Envoy proxy translates HTTP/1.1 browser traffic to HTTP/2 so it works in production. Server reflection lets grpcurl/grpcui discover deployed APIs, deadlines propagate automatically across calls, and a server-side streaming leaderboard pushes live updates (demo shows the stream working). Tooling includes grpcurl/grpcui/bloomRPC for debugging.
AI-written summary · about
chapters (16)
- 0:00Start
- 8:36Define Api Obsessor
- 10:25Leader Board Service
- 20:31Developer Console
- 24:49Gui Tools
- 29:17Api Reflection
- 32:05Dev Tools
- 33:58What Back-End Can Do
- 35:00Deadline Propagation
- 38:04Leaderboards Use Case
- 38:30Balance between Not Sending Too Many Redundant Requests and Displaying Leaderboards
- 39:10Server Side Streaming
- 39:30Add Streaming to Your Leaderboard
- 42:18Dev Console
- 45:55Winner
- 46:34Github Repositories
related talks
15mReact with gRPC
25mgRPC on Web — Lessons & Roadmap
14mOverview of gRPC
28mFrom Backend Powerhouses to Web-Friendly APIs: Unlocking
46mWeb over gRPC: Which Technology to Choose 🕺🏼
26mDemystifying Protocol Buffers and gRPC
46mWeb over gRPC: Which Technology to Choose 🕺🏼
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma