Event-Based Data Synchronization via Push-Pull Notifications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data management systems face challenges in dynamically synchronizing data across multiple data centers in response to events, leading to inefficiencies in reliability, coordination, and synchronization, particularly in cloud-based environments.
Innovation Solution
The implementation of an event-based data synchronization mechanism that utilizes push/pull notifications to dynamically update databases by transmitting metadata and requesting status updates, allowing for real-time synchronization of changed data between source and destination systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional data synchronization methods are used, then data can be transferred between systems, but the synchronization is not real-time and reliability is poor
Solution Approach 1:
The patent implements event-based synchronization where the destination system sends notifications back to the source system about completed synchronization operations. This feedback mechanism allows the source system to track synchronization status and retry failed operations, improving reliability while maintaining near-real-time synchronization through event-driven updates.
Solution Approach 2:
The system pre-establishes synchronization protocols and metadata exchange mechanisms before actual data transfer occurs. The destination system proactively requests synchronization status and sends notifications about completed operations, enabling real-time coordination without waiting for traditional pull-based updates.
2Reliability
If frequent polling for data changes is performed, then synchronization can be maintained, but system complexity and resource consumption increase
Solution Approach 1:
Instead of continuous or frequent polling, the system uses event-driven periodic action where notifications are sent only when data changes occur. The destination system sends notifications about completed synchronization operations at appropriate intervals, maintaining synchronization reliability while avoiding the complexity and resource consumption of continuous polling mechanisms.
3Reliability
If comprehensive data synchronization is implemented, then data consistency is improved, but coordination between multiple data centers becomes more difficult
Solution Approach 1:
The patent segments the synchronization process into discrete events and notifications. Each data change is treated as an independent event that triggers a specific notification sequence between source and destination systems. This segmentation simplifies coordination between multiple data centers by breaking down complex synchronization tasks into manageable, trackable units with clear success/failure states.
Data Source
AI summary
Methods, systems, and devices for data management are described. A cloud data backup and recovery system may include a destination system and a source system. The destination system may be operable to provide backup and recovery services for the source system. The destination system may communicate a set of push/pull notifications with the source system. Each push/pull notifications may indicate an event is being performed in the source system. The destination system may determine an event is being performed in the source system based on transmitting a push notification or receiving a pull notification, where the push or pull notification may include metadata associated with the event. The destination system may retrieve, from the source system, data that is modified by the event based on the metadata. The destination system may synchronize a database of the destination system based on the data retrieved from the source system.