Asynchronous Data Integrity via General Model Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise computing environments, integrating and maintaining data integrity across multiple heterogeneous and independent data systems is challenging due to differences in data formats, technologies, and business rules, leading to difficulties in ensuring consistent data representation and updates across various systems, especially during mergers or acquisitions.
Innovation Solution
A general data model is established to define common data entities and relationships, with a data operation application layer translating between local and general data models, and a data synchronization protocol using XML messages to enforce business rules and ensure data integrity across systems, allowing asynchronous data synchronization and hierarchical communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple heterogeneous and independent data systems are maintained within an enterprise, then system independence and technological diversity are preserved, but data integrity and consistency across systems deteriorate
Solution Approach 1:
The patent introduces a mediator system that includes a general data model and data synchronization protocol acting as an intermediary between heterogeneous data systems. This mediator enables data integrity enforcement without requiring direct integration between systems, allowing them to remain independent while maintaining consistency through the intermediary layer.
Solution Approach 2:
The patent segments the enterprise data architecture into independent data systems that communicate through a standardized interface. Each system maintains its own data model locally while adhering to a general data model framework, allowing segmentation that preserves independence while enabling coordinated data integrity through the standardized protocol.
2Reliability
If data systems are integrated to ensure consistent data representation, then data integrity improves, but system complexity and integration costs increase
Solution Approach 1:
The patent creates a universal data synchronization protocol and general data model that can be applied across multiple different data systems. This universal framework provides multi-functional capability to handle various data types and systems through a single standardized approach, reducing the need for system-specific integration complexity.
Solution Approach 2:
The mediator system with its general data model serves as an intermediary layer that simplifies integration complexity. Rather than creating complex direct integrations between each pair of systems, the intermediary provides a standardized interface that reduces overall system complexity while maintaining data integrity.
3Reliability
If real-time data synchronization is implemented across all systems, then data consistency improves, but processing overhead and system performance deteriorate
Solution Approach 1:
The patent implements periodic data synchronization through scheduled data comparison and update operations. Instead of continuous real-time synchronization, the system periodically checks for changes and propagates updates, maintaining data consistency while reducing the constant processing overhead associated with continuous real-time synchronization.
Solution Approach 2:
The system performs preliminary actions by establishing data change detection mechanisms and synchronization protocols in advance. Changes are identified and prepared for synchronization before actual data conflicts occur, allowing batch processing of updates rather than immediate real-time processing, thus improving performance while maintaining consistency.
Data Source
AI summary
A first database comprises a data entity and a first data model that models the data entity. An agent comprises a data rule concerning the data entity. A plurality of second databases comprises the data entity. A messaging module comprises the agent and is configured to send a message to at least one of the second databases according to the data rule and the general data model.