Skip to main content

21.7 Data Products & Sharing Architecture

A data product is more than a table. It is a governed capability with ownership, context and a defined consumer experience.

Product contract​

Every enterprise data product should state:

  • product name
  • owner
  • domain
  • business purpose
  • source systems
  • grain
  • quality rules
  • freshness
  • security classification
  • consumers
  • support path

Internal sharing​

Use controlled sharing for reusable assets between spaces when producer ownership should remain clear.

External and ecosystem sharing​

Use supported data product and marketplace capabilities when the use case requires discovery, controlled acquisition or broader ecosystem consumption.

Product lifecycle​

Propose -> Design -> Build -> Validate -> Publish -> Consume -> Measure -> Deprecate

Product anti-patterns​

  • unnamed datasets
  • no owner
  • unclear business definitions
  • no quality expectations
  • consumer-specific copies everywhere

Architect exercise​

Take a finance profitability model and redesign it as an enterprise data product consumed by Finance, Supply Chain and SAC.