Registry MDM Pattern

From Glitchdata
Jump to navigation Jump to search

First, we’ll take a look at the Registry style, which is mainly used to spot duplicates by running cleansing and matching algorithms on data from your various source systems.

  • It assigns unique global identifiers to matched records to help identify a single version of the truth.

This style doesn’t send data back to the source systems, so changes to master data continue to be made through existing source systems. Instead, it cleans and matches the identifying cross-referenced information and assumes the source system can manage the quality of its own data.

Information needed to match and provide the link between corresponding records is stored, and a view of this data can be accessed as required.

When a single, comprehensive view of a customer is needed, it uses each reference system to build a 360-degree view in real-time. However, central governance of the data is required to ensure the golden record is reliable.

  • Bi-directional exchange of MDM between hub and spoke systems.
  • No central authority
  • Robust and independent operations


  • If you have a large number of source systems spread across the world, it can be difficult to establish an authoritative source. A Registry style approach can be used to analyze the data while avoiding the risk of overwriting information in the source systems. This will help you avoid potential compliance failure or other regulatory repercussions (which may vary from country to country) that could occur if source data is changed.
  • Registry Style provides a read-only view of data without modifying master data and is a useful way to remove duplications and gain consistent access to your master data.
  • It offers low-cost, rapid data integration with the benefit of minimal intrusion into your application systems.