Data Products 101: From Data Chaos to Clarity
summary
Shows a concrete path: teams write data contract YAML files (ODCS v3.1.0) that codify schema, SLAs, ownership and retention, link to catalogs/GitHub, and run validations so pipelines break loudly not silently. It presents the released Open Data Product Standard (ODPS) 1.0.0 with input/output ports, SBOM support and product metadata, notes vendor integrations (Actun, IBM) and claims weeks-to-months ROI and ~1.5M people impacted so far.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:51Traditional data pipeline problems
- 3:39What is a data contract and why it matters
- 5:47Need for data contract standards
- 7:54Data contracts in practice
- 10:45Key components of a data contract
- 12:10Data contracts to data products
- 13:56Defining data products
- 15:21Open Data Product Standard
- 17:14Belel project overview
- 19:21Belel governance and contributions
- 21:06Future of open standards
- 22:33Value and ROI of data contracts
- 23:57Why data contracts matter
- 25:22Closing remarks
related talks
25mUnpacking The Data Product Experience So Far
29mHow to treat your data as a product
27mThe Data Product ABCs
22mData as a Product: Transforming Analytics for Business Success
01h 00mData Mesh: Beyond the Data Lake
16mProduct Eyes – Seeing Data In A New Light To Build Valuable Products
30mDevOps to DataOps
50mDataOps 101 – A Better Way to Develop and Deliver Data Analytics