Learn vocabulary for designing and describing Data Mesh data products.
0 / 5 completed
1 / 5
What is a 'data product' in Data Mesh?
A data product is a domain-owned, self-contained unit with: data assets, code to produce them, infrastructure, output ports (APIs, files, streams), and quality SLAs — treated like a software product.
2 / 5
What is an 'output port' of a data product?
An output port is the data product's consumer-facing interface: a SQL table, a REST API, a Kafka topic, or a file share. The contract between the data product and consumers is defined at the output port.
3 / 5
What is a 'data product specification' (or data product contract)?
A data product specification defines: the data product's owner, schema of each output port, SLAs (freshness, availability), quality expectations, and access control — enabling consumers to evaluate and use the product.
4 / 5
What does 'data product SLA' refer to in Data Mesh?
A data product SLA is the team's commitment to consumers about data quality characteristics: freshness (how recent is the data?), availability (uptime of output ports), completeness, and accuracy.
5 / 5
What is 'discoverability' of a data product?
Discoverability means potential consumers can find the data product in a catalogue, understand its schema and purpose, and evaluate its suitability — without needing to ask the domain team directly.