Point-to-Point Database Sync with Selective Update Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database synchronization technologies face challenges in maintaining consistency across multiple systems, particularly in the event of connectivity loss, and often require inefficient retransmission of all database files upon reconnection, leading to inefficient use of communication resources.
Innovation Solution
A communication protocol that automatically sets up database pairs for synchronization by exchanging Hello Link-Local Registration Protocol Data Unit (LRPDU) messages, allowing the network protocol to manage synchronization without direct application involvement, and includes mechanisms for record acknowledgment and recovery from connection interruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all database files are retransmitted upon reestablishing connectivity, then database consistency is ensured, but communication resources are inefficiently used
Solution Approach 1:
The patent segments the database synchronization process into individual record-level operations. Instead of treating the entire database as a single unit that must be retransmitted, the system divides data into discrete records and tracks their individual synchronization states. This allows selective retransmission of only those records that are out of sync, rather than retransmitting all database files upon reconnection.
Solution Approach 2:
The patent implements preliminary action by maintaining synchronization state information (such as sequence numbers or checksums) for each record before connectivity is lost. When connectivity is reestablished, this pre-maintained state information enables the system to quickly determine which records need retransmission, avoiding the need to retransmit all records while ensuring consistency.
2Reliability
If application manages database synchronization directly, then synchronization control is precise, but application complexity increases
Solution Approach 1:
The patent extracts the database synchronization management functionality from the application layer and implements it as a separate, dedicated synchronization protocol and system component. The application simply initiates synchronization requests, while the underlying system handles the complex tasks of record-level tracking, state management, and selective retransmission. This separation reduces application complexity while maintaining precise synchronization control through specialized protocols.
Solution Approach 2:
The patent introduces an intermediary synchronization protocol layer between the application and the network communication layer. This intermediary handles the complex coordination of database synchronization, including tracking which records have been synchronized, managing retransmission upon reconnection, and ensuring consistency. The application interacts with this intermediary through simple commands, avoiding direct management of complex synchronization state.
3Loss of energy
If selective retransmission of missing updates is implemented, then network resource usage is reduced, but synchronization protocol complexity increases
Solution Approach 1:
The patent segments database operations into individual record-level units with unique identifiers and state information. This segmentation enables the synchronization protocol to track and manage each record independently, allowing selective retransmission based on individual record states rather than treating the entire database as one unit. The segmented approach makes selective retransmission feasible while maintaining protocol efficiency.
Solution Approach 2:
The patent implements partial action by transmitting only the necessary subset of database records that require synchronization, rather than transmitting all records. The protocol determines which records are missing or out of sync and retransmits only those specific records. This partial retransmission approach reduces network resource usage while the protocol manages the complexity of determining what needs to be transmitted.
Data Source
AI summary
A mechanism includes receiving, at a local node, a Hello message including an application identifier (AppId) and a target link between a target port for a local node and target port for a neighbor node. The local node determines the AppId is associated with an application for performing database synchronization. The local node sets up a local database in memory at the local node as part of a database pair for use by the application, the database pair including a neighbor database at the neighbor node. The local node associates the database pair with the target link. The local node controls synchronization of the local database with the neighbor database via the target link.