Protobuf Editions
summary
Protobuf adds an editions framework that pins exact feature defaults per file, lets codegen and language features be toggled and overridden at file/message/field scopes, and guarantees frozen behavior for an edition’s lifetime. Edition 2023 restores explicit field presence and removes the optional keyword; adoption requires protoc 27+ and plugins that advertise edition support. Google internally migrates hundreds of thousands of protos using an internal transformer called prototiller, and edition 2024 introduces incremental language- and protoc-level features like larger Java enums.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:26Protobuf language history
- 3:36Why Editions were created
- 5:01Editions with feature overrides
- 7:25Editions for API evolution
- 9:13Stability guarantees
- 10:37Proto 2 vs Proto 3
- 12:01Internal rollout and Prototiller
- 13:24Version skew challenges
- 16:34Backward compatibility
- 17:40Third-party tooling support
- 18:46Edition 2024 release
- 20:11Q&A on manage mode
- 20:52Editions and gRPC generator
- 22:57Future Protoc compiler plans
related talks
23mEffective Protobuf: Everything You Wanted To Know, But Never Dared To Ask
35mProtocol Buffers for FHIR
48mProtocol Buffers- A Banked Journey
27mA Programing Language for Data and Configuration!
18mData Integration at SafetyCulture: Implementing Protobuf for Efficient Data Contracts
31mProfiling Formats and Why You Should Care
36mIntergalactic dataspeak
25mFrom Guesswork to Governance: Bringing API Discipline to Data Streaming