Data Product

Origin & evolution

The term comes from Zhamak Dehghani, who defined data mesh in 2019 while a principal consultant at Thoughtworks and developed its principles through 2020. "Data as a product" is one of the four principles, alongside domain ownership, a self-serve platform, and federated computational governance. The argument is that applying product thinking to analytical data, with owners and consumers and quality bars, fixes the neglect that central data lakes tend to breed. She set it out in full in Data Mesh (O'Reilly, 2022). Practice since has tempered the more ambitious org-restructuring claims, while the data-product unit itself has stuck.

How it works in practice

A logistics company's fulfilment domain owns a delivery_performance data product. It publishes a documented table updated hourly, with a stated freshness SLA and a named owner. A finance dashboard🎛️DashboardData & AnalyticsAn analytics dashboardView reference → and a customer-facing tracking service both consume it. When finance needs a new field, it files a request against the product's owner rather than reverse-engineering a raw warehouse table. The fulfilment team treats those consumers as customers: a breaking change goes through deprecation, not a surprise.

Data product vs. its neighbours

• Data source🛢️Data SourceData & AnalyticsA data source or integrationView reference → is raw input, the system of record a pipeline reads. A data product is a curated, owned output built to be consumed, often assembled from several sources.
• Data domain🏷️Data DomainData & AnalyticsA logical grouping of related data assetsView reference → is the organisational boundary that owns products. The domain is the team and its remit; the product is the specific asset it ships.
• Dashboard is one way to consume a data product. A dashboard presents; a data product is the governed dataset behind it that many dashboards and services can share.

In the graph

In the Unified Product Graph, a data product anchors part of the data and analytics region exactly as data mesh frames it. A domain produces it (data_domain_produces_data_productData DomainproducesData Producthierarchy), a pipeline feeds it (data_pipeline_feeds_data_productData PipelinefeedsData Productcross-domain), it serves dashboards (data_product_serves_dashboardData ProductservesDashboardcross-domain), and services consume it (data_product_consumed_by_serviceData Productconsumed byServicecross-domain). Those edges encode the contract Dehghani describes: every data product has a clear producer, a feeding pipeline, and named consumers, so an orphaned product with no consumer is visible at a glance.