MDM architecture for a data mesh
Given the distributed nature of a data mesh, each data product needs to ensure that the master data they are using are consistent and accurate. This mandates a need for a reference master dataset that is centrally maintained and referenced by all the data products and their pipelines that need to ensure consistency. Multiple architectures are available for managing this central reference dataset. To understand what design works best for you, you should first examine your master data. Not all master data is used by every domain in the company. Customer master data might not overlap product master data, but the sales domain might use both.
Hence, two strategies emerge for managing master data: domain-oriented MDM and domain-level MDM:
Figure 10.2 – Domain-oriented MDM
The domain-oriented technique has a single MDM domain that is referenced by all the data products across all the data landing zones, as shown in Figure...
