Schema evolution across teams
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
change event schemas without breaking consumers you cannot coordinate with.
Planned topics
- Compatibility modes: backward, forward, full; pick one per topic and enforce in a registry.
- Safe changes: add optional fields; unsafe: rename, remove, change meaning.
- Breaking change: publish a new versioned topic or event type and run both during migration.
- Set a deprecation window and measure remaining consumers.
Draft outline details
Demonstration
schema registry compatibility check in CI failing a PR that renames carrierCode; a topic pair shipment-dispatched.v1 and .v2 with a sunset date.
Check your understanding
Name a safe schema change.
Show answer
Adding an optional field with a default.
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.