Data modelling - Process
Schema evolution
Changing a data structure over time without unnecessarily breaking its users
What's it for?
Allows data structures to change as needs evolve while reducing the chance of breaking existing users or systems.
For example…
A data team adds a new optional `deliveryMethod` field to an event schema without breaking older consumers that do not yet use it
Schema evolution rules let a producer add fields gradually while keeping existing dashboards and integrations working during the transition