Database Synchronization via Waiting Queue Rearrangement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database synchronization mechanisms often result in data misalignment and poor data identity due to their dependency on the source database, leading to issues during the synchronization process.
Innovation Solution
A method involving reading data from a first database, capturing a dynamic data log, joining it to a waiting queue, determining and rearranging dislocation data categories, and synchronizing the rearranged data to a second database using a LinkedIn data bus and RabbitMQ engineering cache, ensuring accurate data synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing database synchronization mechanism is used, then data synchronization is achieved, but data misalignment occurs and data identity cannot be ensured
Solution Approach 1:
The patent introduces a waiting queue as an intermediary component between the source database and target database. Data is first written to the waiting queue before being synchronized to the target database, ensuring proper sequencing and preventing data misalignment. This mediator buffer resolves the contradiction by decoupling the write and sync operations.
Solution Approach 2:
The patent performs preliminary actions by capturing data logs and determining dislocation categories before actual data synchronization. The system identifies potential data misalignment issues in advance and rearranges dislocated data before syncing to the target database, ensuring data identity is maintained throughout the synchronization process.
2Speed
If data is synchronized directly from source database, then synchronization speed is fast, but data dislocation occurs
Solution Approach 1:
The waiting queue serves as a mediator that accepts data rapidly from the source database while maintaining proper sequencing information. This allows fast data ingestion without losing track of data order, resolving the conflict between speed and sequencing accuracy.
Solution Approach 2:
The system performs preliminary classification of data into dislocation categories and captures data logs before synchronization. This preliminary processing enables the system to identify and correct sequencing issues before data is written to the target database, maintaining both speed and accuracy.
3Reliability
If data rearrangement is performed, then data identity is ensured, but processing complexity increases
Solution Approach 1:
The patent segments data into different dislocation categories based on the type of dislocation detected. By categorizing data differently, the system can apply appropriate rearrangement strategies for each category, making the complex rearrangement process more manageable and systematic.
Solution Approach 2:
The system performs preliminary classification and identification of dislocation categories before actual data rearrangement. This preliminary sorting simplifies the subsequent rearrangement process by organizing data in a way that makes it easier to identify and correct specific types of dislocations.
Data Source
AI summary
A terminal, a storage medium, and a database synchronization method thereof are disclosed. The database synchronization method includes reading data from a first database and capturing a dynamic data log in the first database; joining data to a waiting queue read from the first database; determining a dislocation category of the data in the waiting queue, and rearranging the dislocation data in the waiting queue into a first category according to the dynamic data log; and synchronizing the rearranged data to a second database. According to the database synchronization method provided by the present invention caches the data read from the first database to the waiting queue, and dislocation data in the waiting queue is rearranged and then synchronized to the second database, so that a problem of poor data identity after database synchronization is avoided.