Practice mesh topology vocabulary: data mesh vs. data lake vs. data warehouse, domain-oriented decentralized ownership, self-serve platform, and organizational paradigm concepts.
0 / 5 completed
1 / 5
A colleague says 'Data mesh is an organizational paradigm, not just a technology.' What do they mean?
Data mesh is fundamentally about organizational change — distributing data ownership to domain teams, applying product thinking to data, and enabling federated governance. Technology is an enabler, not the core of the paradigm.
2 / 5
What is 'domain-oriented decentralized ownership' in data mesh?
Domain-oriented decentralized ownership means that the business domain closest to the data — like the orders team owning order data — is responsible for producing and maintaining that data as a product, rather than a central data team.
3 / 5
How does a data mesh differ from a data lake?
A data lake centralizes all raw data in a single storage layer, typically managed by a central data engineering team. A data mesh decentralizes ownership — each domain team manages and serves their own data products through defined interfaces.
4 / 5
What does a 'self-serve data platform' provide in a data mesh?
The self-serve data platform is one of the four principles of data mesh. It provides domain teams with the infrastructure, tooling, and templates they need to create and operate data products independently — lowering the technical barrier to data ownership.
5 / 5
When comparing data mesh to a data warehouse, which statement is most accurate?
A data warehouse centralizes transformed, business-ready data under a central team's control. Data mesh distributes this responsibility — domain teams model and serve their own data, potentially serving it in warehouse-compatible formats but owning the process themselves.