Talking to Go gRPC Services Via HTTP/1
summary
A Go library implements automatic gRPC-Web downgrading by running an in-memory reverse proxy next to the client that injects an Accept header, detects missing TE: trailers (incompatible proxies like AWS ALB), and transcodes gRPC ↔ gRPC‑Web by packing/unpacking trailers as the last message. It requires minimal code changes, preserves normal grpc.Dial usage, supports unary and server-streaming only today (no client streaming yet), is published on GitHub under Apache‑2, and works in demos and real deployments.
AI-written summary · about
chapters (10)
- 0:00The problem with gRPC
- 1:08Load balancer compatibility
- 1:41Exploring alternative solutions
- 4:21REST API drawbacks
- 6:02HTTP/2 vs HTTP/1 features
- 9:04Introduction to gRPC-Web
- 10:27Automatic gRPC-Web downgrading
- 13:25Implementation details
- 17:09Using the open source library
- 19:23Future work and conclusion
