DataEngBytes 2023 - BRI-T1-01 - Chad Sanderson
summary
Argues that API-style data contracts — a YAML contract spec plus CI/CD PR checks tied to schema, semantics and SLAs — prevent churn and costly outages at Convoy, catching ~50% of quality incidents before production and avoiding six‑figure failures caused by dropped columns. Implementation uses a Git repo of contracts, tiered enforcement (0/1/2), Amundsen catalog enrichment, and subscriber alerts; start vertically on business‑critical pipelines and expand incrementally.
AI-written summary · about
chapters (15)
- 0:00Data quality for AI
- 2:34Data quality critical for AI
- 5:46Root causes of data quality issues
- 8:57Human challenges behind poor data quality
- 12:54Why current solutions fail
- 16:06What is a data contract
- 21:31Benefits of data contracts
- 22:13Implementing data contracts
- 26:03Starting data contract rollouts
- 29:36Changing culture with data contracts
- 33:10Data contracts with SaaS
- 35:39Challenges for large orgs
- 37:27Data contracts vs data mesh
- 38:33Balancing quality and velocity
- 39:17Scaling data contracts
related talks
30mDataEngBytes 2023 - PER-T1-01 - Chad Sanderson
28mDataEngBytes 2023 - SYD-T1-03 - Chad Sanderson
20mDataEngBytes 2023 PER-T1-10 - Matthew Carter
21mDataEngBytes 2023 - SYD-T3-04 - Abhinav Goyal
27mLive in the Data Wild West: The Data Contracts Sheriff
31mData Reliability Engineering: Secret Of Our Success
20mData Contracts: Keep Your Weekend Work-Free!
26mData contracts: driving data culture change
