Learn vocabulary for discussing the migration from centralised data architectures to Data Mesh.
0 / 5 completed
1 / 5
What is 'domain identification' in a Data Mesh migration?
Domain identification maps the organisation's business areas (Orders, Customers, Finance, etc.) to data domains — defining who will be responsible for which data products in the new architecture.
2 / 5
What is a 'pilot domain' in a Data Mesh migration?
A pilot domain is the first domain to implement Data Mesh — chosen for its business importance, team maturity, and manageable complexity. Learnings from the pilot inform the broader rollout.
3 / 5
What is 'data product migration' in a Data Mesh transition?
Data product migration transforms existing centralised data assets (ETL jobs, data warehouse tables) into domain-owned data products — adding ownership, SLAs, documentation, and proper interfaces.
4 / 5
What is the 'strangler fig pattern' applied to Data Mesh migration?
The strangler fig pattern in Data Mesh migration means incrementally building domain data products that replace centralised ETL pipelines and warehouse tables — without a big-bang cutover.
5 / 5
What is 'data platform readiness' in a Data Mesh migration?
Data platform readiness assesses whether the self-serve infrastructure platform (data pipeline tools, data catalogue, monitoring, access control) is mature enough to support domain teams without requiring deep data engineering skills.