Customer 360 & Real-Time Risk Intelligence Platform · View 10 of 20

Schema and Data Contract Lifecycle

How a schema change is proposed, checked for compatibility, registered, rolled out to producers and consumers, and eventually deprecated.

Editable source SVG draw.io All views

Compatibility rule

BACKWARD compatibility enforced in CI — a consumer on the old schema must still read
Additive changes flow through automatically; breaking changes require a new topic version
In-place overwrite of a registered schema is blocked at the registry

Rollout order

Producers upgrade first, consumers follow — never the reverse
Delta tables evolve by column addition, preserving existing readers
Old versions are deprecated after 90 days of zero observed usage

Governance

Contracts are owned by the producing team and reviewed by the consuming domain
Version adoption is monitored, so deprecation is evidence-based, not calendar-based
The registry, not a document, is the authoritative record of every contract