DataEngBytes 2023 - SYD-T1-03 - Chad Sanderson
summary
Defines data contracts as API-like agreements that declare schema semantics and SLAs and enforces them programmatically via YAML contract per resource with a one-to-one mapping and consumer-proposed ownership, tiered actions (0–2) and CI CD checks that either block or notify changes. Implementation uses GitHub PR workflows to show exactly which fields break, integrates with catalogs like Amundsen indexing, and ties monitors into the contract platform. Deployed ~15 times, spoken with ~800 companies, and typically cuts data quality incidents by about 50% immediately.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:25AI impact on data quality
- 5:42Why data quality is low
- 8:09Organizational causes of issues
- 12:24Monitoring and governance limits
- 14:55Data contracts explained
- 20:14Implementing data contracts
- 23:46Contracts with data catalogs
- 25:10Changing culture with contracts
- 27:20Summary and Q&A
related talks
41mDataEngBytes 2023 - BRI-T1-01 - Chad Sanderson
30mDataEngBytes 2023 - PER-T1-01 - Chad Sanderson
27mLive in the Data Wild West: The Data Contracts Sheriff
20mDataEngBytes 2023 PER-T1-10 - Matthew Carter
36mDataEngBytes 2023 - PER-T1-02 - Josh Armitage
20mData Contracts: Keep Your Weekend Work-Free!
30mDataEngBytes 2023 - MEL-T1-03 - Adric Streatfeild
26mData contracts: driving data culture change
