GRPC & Go
summary
Argues that switching from JSON to gRPC solves parsing, typing, documentation and compatibility pain points by using protobuf-defined messages, code generation and HTTP/2. Shows concrete features: auto-generated Go code includes comments for godoc, three streaming modes (server, client, bidi) for uploads/downloads, reserved field numbers and an unknown fields container that preserves unrecognized fields, and HTTP/1->gRPC transcoding via gRPC Gateway or Google Endpoints/istio. Claims setup is straightforward and generated code removes hand-rolled parsing.
AI-written summary · about
chapters (6)
- 0:00Introduction and JSON issues
- 1:43Defining services and messages
- 3:27Advantages and compatibility
- 4:45Managing schema changes
- 5:42Introduction to transcoding
- 6:01Transcoding solutions and wrap up
related talks
42mgRPC and Go: Developing Efficient and Type-Safe Services
37mgRPC Intro
33mIntro to gRPC
22mGRPC: Lightning fast self documenting APIs
13mFrom Writing REST to Writing gRPC
25mgRPC on Web — Lessons & Roadmap
35mShow Me the Schema! RPCs and Learning to Love Code Gen
27mEvolution of serialization formats and usage in Go