How it works
Why does it behave this way?
- 1
A new kind of problem
What makes a schema change a multi-party coordination problem with no atomic update?
- 2
Identity
How does a reader map bytes to fields, and why is position-based identity silently fatal?
2 pages - 3
Where structure is bound
Why is validation work only ever moved, and why is binding a per-field decision?
3 pages - 4
Compatibility
What do backward, forward and full compatibility each allow, and why must the check be transitive?
5 pages - 5
Enforcement
What happens when the schema registry is down?
4 pages - 6
Evolution at scale
Why do you migrate the schema rather than the data, and what invariant follows?
3 pages - 7
What schema evolution forbids
What can never be done with schemas, and what does each escape cost?