Unpacking The Data Product Experience So Far
summary
Data products are practical artifacts not vague concepts: a text file with declarations that starts compute, runs code, tags catalogs and pushes policies, stored in Git for versioning and CI/CD. Three useful types appear: source-aligned / consumer-aligned / aggregate. Design expects products that span the operational and analytical planes, live as modules in pipelines, and get maintained by domain “personal trainers.” Success ties to usage metrics drive value and to technologies that let domains build and iterate fast.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:06Data Mesh Community
- 3:35What Is a Data Product
- 4:54Metadata
- 5:34Access Pattern
- 8:06Data Product Definitions
- 11:48Governance
- 15:31Who Builds Data Products
- 17:03Cognitive Load
- 17:45Hub and Spoke Model
- 18:15Central Enabling Team
- 20:58Consumer Align Data Products
- 21:20Aggregate Data Products
- 21:57Data Pipelines in a Data Mesh
- 22:16Data Products Are Modules in a Data Pipeline
- 24:12Data Product Security
related talks
22mData as a Product: Transforming Analytics for Business Success
30mData Products 101: From Data Chaos to Clarity
40mData Products and AI: A Conversation on Success Factors and Hurdles
29mHow to treat your data as a product
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy
49mPanel discussion - Building Data Products
13mData for product
19mDevDataOps - Data-Driven Product Development for Software Engineers