Master Data Schema Augmentation via Centralized Registry
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge lies in synchronizing and augmenting database schema across multiple applications that use shared master data, where changes in the data or schema can occur independently, leading to desynchronization and inconsistent data usage.
Innovation Solution
A master data synchronization system that includes a cloud adapter, synchronization platform, and master data store, which extracts, processes, and transmits schema and data changes, allowing for centralized near-real-time management and augmentation of the schema to maintain consistency and enhance data usability across applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If each application maintains its own local copy of master data and updates independently, then each application can operate autonomously, but schema desynchronization and data inconsistency occur across applications
Solution Approach 1:
The patent introduces a schema registry as an intermediary component that centralizes schema storage and management. The registry receives schema definitions from master data sources and distributes them to multiple applications, ensuring all applications access the same authoritative schema version without requiring direct peer-to-peer synchronization.
Solution Approach 2:
The system performs preliminary schema validation and registration before data operations occur. Schema definitions are registered and validated in advance in the schema registry, and applications retrieve approved schemas before processing data, preventing inconsistent data operations from occurring in the first place.
2Reliability
If a centralized schema registry is implemented to maintain consistency, then data consistency across applications is improved, but system complexity and resource consumption increase
Solution Approach 1:
The schema registry is designed to serve multiple applications simultaneously with a single centralized repository. Rather than implementing separate schema management systems for each application, the registry provides universal schema services to all applications, reducing overall system complexity through consolidation.
Solution Approach 2:
Applications retrieve copies of schema definitions from the centralized registry rather than maintaining unique schema instances. This copying approach allows applications to operate with local schema copies for efficiency while ensuring consistency with the central registry, reducing the need for complex real-time synchronization mechanisms.
3Reliability
If schema changes are propagated to all applications immediately, then data consistency is maintained, but processing time and computational resources increase
Solution Approach 1:
The system implements periodic schema synchronization where applications retrieve updated schemas at scheduled intervals rather than continuously. The schema registry maintains versioned schemas and applications can periodically check for updates, balancing synchronization freshness with reduced processing overhead compared to continuous real-time synchronization.
Solution Approach 2:
The schema registry implements a feedback mechanism where applications notify the registry of their schema version status. The registry tracks which applications have which schema versions and can target updates efficiently, reducing unnecessary propagation to applications that already have current schemas and minimizing overall synchronization time.
Data Source
AI summary
Example embodiments for augmenting master data schema are described. In an example embodiment, schema of master data to be employed by a plurality of applications are accessed. First additional information is added to the schema, wherein the first additional information is to be employed by each of the plurality of applications in accessing the master data. After the adding of the first additional information, second additional information is added to the schema, wherein the second additional information is to be employed by a first corresponding one of the plurality of applications in accessing the master data. In some example embodiments, third additional information is added to the schema, wherein the third additional information is to be employed by a second corresponding one of the plurality of applications in accessing the master data.