Client-Based Cross-Region Data Replication via Broadcast Notifications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional replication techniques for databases across geographic regions face inefficiencies due to high latency in communication and suboptimal conflict resolution methods, particularly when dealing with updates and deletions across geographically dispersed data collections.
Innovation Solution
A client-based architecture utilizing a broadcast communications channel for notifications of changes, with conflict resolution rules applied to manage updates and deletions, including a 'last-write wins' policy and maintaining deleted items to resolve conflicts, ensures efficient data replication between regions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional log shipping replication is used to replicate databases across geographic regions, then data backup and availability are improved, but communication latency and replication efficiency deteriorate
Solution Approach 1:
The patent extracts the replication control logic from the database administrator's manual control to an automated system. The replication manager automatically identifies changes in the source database and propagates them to target databases, eliminating the need for manual intervention and reducing replication latency while maintaining data availability across geographic regions.
Solution Approach 2:
The patent implements a feedback mechanism where the replication manager continuously monitors the source database for changes and automatically triggers replication operations. This feedback loop ensures that data is replicated promptly upon change detection, reducing communication latency while maintaining reliable data availability across distributed locations.
2Adaptability or versatility
If manual control by database administrator is used for replication, then customization flexibility is improved, but operational complexity and time consumption worsen
Solution Approach 1:
The patent enables the replication system to serve itself by automatically detecting database changes and initiating replication operations without requiring database administrator intervention. The replication manager autonomously manages the replication process, reducing operational complexity while maintaining the ability to customize replication parameters through initial configuration.
3Stability of the object's composition
If all operations are replicated to secondary database using log shipping, then data consistency is improved, but network bandwidth consumption and replication overhead worsen
Solution Approach 1:
The patent extracts only the essential change information from the source database and propagates selectively to target databases. By identifying and replicating only the necessary data changes rather than all operations, the system maintains data consistency while reducing network bandwidth consumption and replication overhead.
4Reliability
If conventional replication techniques are used, then data backup capability is improved, but conflict resolution efficiency and data synchronization worsen
Solution Approach 1:
The patent applies conflict resolution rules in advance by maintaining deleted items in the source database before replication occurs. This preliminary action allows the system to pre-determine the correct version of data during replication, improving conflict resolution efficiency while maintaining reliable data backup capabilities across geographic regions.
Data Source
AI summary
One or more computing nodes located in a first region may maintain a first collection of data items. A second set of one or more computing nodes in a second region may maintain a collection of data items that is at least a partial replica of the first collection. Notifications of changes to the first collection may be transmitted, via a broadcast communications channel, to a replication module, which may be included in a client application. The replication module may transmit requests to update the second collection of data based on changes to the first collection. Conflicts may be resolved through a last-write wins policy.