Master Data Management Using Judgment-Based Unification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Master Data Management (MDM) solutions face issues with obtrusiveness, slow responsiveness, high resource overhead, and computational complexity due to the need for centralization and synchronization of disparate databases, as well as difficulties in creating golden records using Change Data Capture (CDC)-based approaches.
Innovation Solution
The introduction of representing MDM records as a set of judgments and achieving 'MDM consistent states' by unifying updates from component databases, ensuring referential integrity, and propagating changes to maintain synchronized data across all systems, using CDC mechanisms or event streaming technologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional MDM solutions centralize disparate databases to a central master database, then data consistency is improved, but system responsiveness deteriorates and resource overhead increases
Solution Approach 1:
The patent divides the centralized master database into multiple distributed component databases, each maintaining local copies of master data. This segmentation allows systems to access local data without centralized coordination overhead, improving responsiveness while maintaining consistency through distributed synchronization mechanisms.
Solution Approach 2:
The patent introduces an MDM hub as an intermediary that coordinates data sharing between component databases without requiring full centralization. The hub manages data exchange and consistency protocols, enabling distributed systems to maintain data consistency while avoiding the performance penalties of centralized architecture.
2Reliability
If conventional MDM solutions synchronize multiple disparate databases, then data consistency is improved, but computational complexity increases
Solution Approach 1:
The patent changes the synchronization model from continuous full synchronization to event-driven incremental synchronization. Component databases notify the MDM hub only when data changes occur, and synchronization is performed selectively based on change events. This reduces computational complexity by processing only necessary updates rather than continuously synchronizing all data.
Solution Approach 2:
The patent implements periodic consistency checks and synchronization cycles rather than continuous synchronization. The MDM hub periodically reconciles data across component databases at scheduled intervals or triggered by specific events, reducing computational overhead compared to constant synchronization while maintaining acceptable consistency levels.
3Productivity
If CDC techniques are used to capture changes in various databases, then data capture efficiency is improved, but golden record creation becomes difficult
Solution Approach 1:
The patent merges change data captured from multiple component databases at the MDM hub, where CDC mechanisms capture changes efficiently from each source. The hub consolidates these changes, applies conflict resolution rules, and creates unified golden records by combining data from multiple sources according to predefined business logic and data quality rules.
Solution Approach 2:
The patent implements feedback loops where the MDM hub monitors data changes captured by CDC mechanisms, evaluates changes against golden record criteria, and triggers golden record creation or updates when appropriate conditions are met. This feedback mechanism automates the golden record creation process based on captured changes rather than requiring manual intervention.
Data Source
AI summary
Disclosed embodiments are related to Master Data Management (MDM) technologies. Each DB entity (record) in component databases (DB) is represented as a judgment, and an MDM system unifies judgments obtained from the component DBs into a unified set of judgments. In the unified set of judgments, linkages are judgments asserting that particular DB entities from different DBs are the same/similar, and a golden record comprises field values describing each of the DB entities. In making judgments, the MDM system consolidates judgments (or records) describing the same subject into a single judgment, and performs updates to field values in a manner that does not violate referential integrity. Each update is associated with an MDM consistent state. Updates in the form of judgments are provided to the relevant component DBs, which are converted into serializable transactions associated with respective MDM consistent states. Other embodiments may be described and/or claimed.