gRPC vs REST Wire Format
📍 Used after slide 26-28
Loading diagram…
Side-by-side comparison: JSON ~400 bytes vs Protobuf ~40 bytes, HTTP/1.1 vs HTTP/2.
Speaker Notes
Walk-through: Left side shows REST characteristics: HTTP/1.1, JSON text payloads (~400 bytes), new connection per request, and SSE/WebSocket for streaming. Right side shows gRPC: HTTP/2, binary Protobuf (~40 bytes), persistent multiplexed connections, and 4 built-in streaming modes.
Important caveat: gRPC unary is SLOWER than REST on localhost because network cost is zero. gRPC wins at high concurrency and streaming, and in production with pod-to-pod latency.