Pattern 91 / SCHEMA

Schema Versioning

Use this when Changing data contracts without breaking old readers.

Pressure
Changing data contracts without breaking old readers
Mechanism
Use additive changes, versioned readers, migrations, and compatibility windows
Toll
Old versions and migration states must be actively retired
Architecture plate91
Diagram for Schema Versioning
Executive brief

Schema Versioning fits when Changing data contracts without breaking old readers. Mechanism: Use additive changes, versioned readers, migrations, and compatibility windows. Use it for APIs, events, databases, warehouses. The toll: Old versions and migration states must be actively retired.

Use when

Apis, events, databases, warehouses.

Example

Use schema versioning when apis, events, databases, warehouses..

Review framing

Describe the pressure first, then the mechanism, then the cost. That keeps the design grounded.

Same pressure family

Data Evolution

92Expand-Contract Migration93Tombstone
← 9092 →