Data Contracts VS Data Chaos: A Survival Story
summary
Claims a pragmatic path from napkin to registry: start with a humble empty document as a machine-readable data contract, register it centrally, version it, and run an expansion contraction cleanup lifecycle for breaking changes. Uses schema plus semantics, CI hooks and lightweight AI assistants (Diplomat, Artisan, Sentinel). Zalando scale numbers shock: 300 teams producing, 6,000 data products and automated registry plus contract-driven alerts actually reduce firefighter archaeology.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:33Coffee machine crisis
- 4:22Mesopotamia and trust
- 9:50Modern data tribes
- 15:57Data contracts solution
- 21:17Four demons of adoption
- 22:00Superficiality and schema
- 26:40Gigantism and trust
- 34:39Staticity and versioning
- 41:49AI hype and automation
- 46:06Trust over contracts
- 47:49Q&A
related talks
42mData Contracts Are Good for AI
27mLive in the Data Wild West: The Data Contracts Sheriff
32mData Contracts: Consensus as Code
39mTaming the Chaos: Open Standards for Data Contracts and Products Are the Back...
44mBring data teams together with data contracts
30mContracts, Schema Evolution in Data Pipelines
30mExpand Contract Pattern for Continuous Delivery of Databases
47mData governance