Master Data Synchronization via Centralized Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge lies in maintaining synchronization of dynamic master data and its schema across multiple applications, as changes in the master data and schema can occur at different times, leading to inconsistencies and lack of synchronization.
Innovation Solution
A master data synchronization system that includes a cloud adapter, synchronization platform, and master data store, which processes and stores master data and schema, allowing for near-real-time updates and augmentation, while caching only the schema to reduce resource consumption and facilitate frequent access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If each application maintains its own local copy of master data and updates it independently, then each application can access data quickly without network latency, but synchronization consistency across applications deteriorates and data inconsistencies arise
Solution Approach 1:
The patent introduces a master data service as an intermediary component that manages master data centrally. This service receives requests from multiple applications, maintains the authoritative copy of master data, and distributes updates to all applications. The intermediary resolves the contradiction by providing fast local access through a standardized interface while ensuring centralized control for synchronization consistency.
Solution Approach 2:
The patent merges the master data storage and management functionality into a single centralized service that serves multiple applications. Instead of each application maintaining separate local copies, the master data service consolidates the master data repository, enabling all applications to access the same authoritative data source while maintaining synchronization through unified update management.
2Reliability
If master data and schema changes are propagated to all applications immediately, then synchronization consistency is improved, but system complexity and resource consumption increase
Solution Approach 1:
The patent implements preliminary action by maintaining a centralized registry of all applications that consume master data. Before propagating schema or data changes, the master data service consults this registry to identify which applications need to be updated. This preliminary identification step simplifies the propagation process by providing a ready-made distribution list, reducing the complexity of tracking and notifying all affected applications.
Solution Approach 2:
The patent employs feedback mechanisms where applications register their data consumption requirements with the master data service. The service uses this feedback information to determine the scope and method of change propagation. When changes occur, the service leverages the registered feedback data to efficiently target only the necessary applications, thereby reducing unnecessary system complexity and resource consumption.
3Reliability
If all applications update their local databases simultaneously when master data changes, then data consistency is improved, but the risk of conflicts and errors increases
Solution Approach 1:
The master data service acts as a mediator that controls and coordinates all updates to master data. When changes are needed, the service implements them centrally and then propagates the updates in a controlled manner to all registered applications. This intermediary control prevents simultaneous conflicting updates by ensuring that only one authoritative update occurs at a time, thereby reducing conflict and error risk while maintaining data consistency.
Solution Approach 2:
The patent applies preliminary action by validating and preparing master data changes before propagating them to applications. The master data service performs change validation, schema verification, and update preparation in advance, ensuring that changes are error-free before distribution. This preliminary validation step prevents harmful conflicts and errors from occurring during the update propagation process.
Data Source
AI summary
Example embodiments for master data synchronization for multiple applications are described. In an example embodiment, master data to be employed by a plurality of applications, as well as schema for the master data, are accessed. One or more publication requests to store the master data and the schema of the master data to a master data store accessible by the plurality of applications are generated. The schema may be cached locally to one or more of the applications.