System Design · Senior · Question 74 of 75
How do you evolve event or message schemas without breaking consumers?
- ✓Correct answer: Only make backward/forward compatible changes (add optional fields, never reuse or retype field numbers/names) and version breaking changes
- 2Change fields freely and redeploy all consumers simultaneously
- 3Stop sending events during changes
Explanation
Producers and consumers are deployed independently; schema registries can enforce compatibility rules.