Wire-Contract Design
The contract the bytes actually implement: how null, absent, and default are told apart, what a reader does with fields it does not know, and where one message ends. These edge cases cause outages.
part ofData serializationoverview, primer and where to startread it →on this pageshowhide
explore
- Nullability and Optionality5 questions
- Defaults and Unknown Fields5 questions
- Framing and Envelopes5 questions
- IDLs and Code Generation6 questions
- Numeric and Temporal Fidelity6 questions
- Deterministic Canonical Encodings4 questions
- AI & Data Scientistrole
- API Designskill
- Backend Developerrole
- Blockchain Developerrole
- Computer Scienceskill
- Data Analystrole
- Data Engineerrole
- Forward Deployed Engineerrole
- Full Stack Developerrole
- Game Developerrole
- Java Backend Developerrole
- Kotlin Backend Developerrole
- Machine Learning Engineerrole
- Server-Side Game Developerrole
- Software Architectrole
questions
page 2 of 2Across a pipeline of services on different schema versions, how would you set one policy for unknown-field handling?
level: principalimportance: nice to knowfreq 30%
basics
~20 sClassify edges rather than services: strict at boundaries where a human or tool authored the input, preserve-and-forward on internal transit hops, drop at terminal sinks. Then make the policy real with a conformance fixture, a per-hop counter, and a named owner.
showing 31–31 of 31