JSON is Great, but Protobufs Make It Faster
summary
Shows how Protocol Buffers replace JSON by compiling a .proto schema into language-specific bindings (C++, Java) and sending a binary payload over the network, with concrete numbers: 3x faster serialization (JSON 91 ms vs Protobuf 30 ms), 13x faster deserialization (JSON 50 ms vs Protobuf 4 ms), and 40% smaller payloads (JSON 9000 B vs Protobuf 5500 B). Explains required/optional fields, backward compatibility, and that real microservices (LinkedIn example) see large latency reductions.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 0:51Why JSON has scaling issues
- 3:10Introducing Protocol Buffers
- 5:15How Protocol Buffers work
- 7:41Defining Protobuf schemas
- 9:27LinkedIn’s Protobuf success case
- 10:56Performance comparison numbers
- 13:07When to use Protobufs
- 15:54Q&A session
related talks
35mBeyond JSON: Improving inter-app communication
29mBinary Protocols - The Current State of Affairs
11m"RPC Frameworks Overview"
38mA Quick Guide to RPC Frameworks
46mIntroduction to gRPC
49mBuilding fast microservices with binary protocol - introduction to gRPC
46mA Different Kind of Networking with gRPC and Protocol Buffers
34mRuby and gRPC
