"RPC frameworks overview"
summary
A production migration replaces dozens of JSON HTTP calls with gRPC over ActiveMQ, connecting 50+ services via persistent clients to a Go gRPC server and cutting traffic and costs by sending much smaller protobuf messages; the system handles about 300 events/day during testing and resolves heartbeat/subscription flakiness. gRPC’s proto compiler generates Ruby encoders but Ruby gems lagged (a two‑week upgrade delay); gRPC offers full‑duplex HTTP/2 (some load balancers don't handle it), Twirp is HTTP/1 + protobuf without duplex, Thrift and Avro remain useful for multi‑language shops.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:39Understanding RPC
- 2:44Real-world migration case
- 5:26System design benefits
- 7:25Protobuf mechanics
- 10:35gRPC features and pros/cons
- 18:36Alternative frameworks
- 20:26Apache Thrift overview
- 24:32Cap'n Proto analysis
- 27:07Other RPC solutions
