Compatibility policies
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
write rules for what changes are allowed without coordination.
Planned topics
- Backward compatible: new producer, old consumer still works; forward: old producer, new consumer works.
- Safe: add optional fields; risky: remove, rename, change type or meaning.
- Policy: compatibility mode per subject in the schema registry; additive-only by default.
- Meaning changes are breaking even when the schema is unchanged.
- Define deprecation windows and sunset notices.
Draft outline details
Demonstration
a policy table: change type, allowed without notice, needs notice, requires new version.
Check your understanding
Is changing a field's meaning but not its type compatible?
Show answer
No; it breaks consumers although the schema validates.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.