Database Synchronization Using Preliminary Action
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data synchronization methods between source and target database systems often induce latency and unequal system utilization, particularly for long-running transactions, as they require gathering all data changes before applying them, which can lead to high processing overhead and network traffic.
Innovation Solution
The method allows for the synchronization of both committed and uncommitted database transactions by applying accumulated changes to the target database system before they are committed, reducing latency and optimizing system utilization by performing processing and application steps in parallel.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data synchronization waits for transaction completion before applying changes, then data consistency is ensured, but replication latency increases
Solution Approach 1:
The patent applies preliminary action by capturing and applying data changes to the target database before the source transaction is fully committed. The system captures changes during the transaction processing phase and applies them to the target database in advance, reducing replication latency while maintaining consistency through proper transaction coordination.
2Device complexity
If the system processes only committed transactions, then processing overhead is reduced, but system utilization becomes unequal
Solution Approach 1:
The system performs preliminary capture and application of changes during the transaction processing phase, before commitment is finalized. This allows the target database to be updated in advance, balancing the processing workload and improving overall system utilization by preventing the target system from sitting idle waiting for committed transactions.
3Reliability
If all data changes are gathered before replication, then data integrity is maintained, but network traffic increases
Solution Approach 1:
The patent implements preliminary action by capturing changes during transaction processing and applying them to the target database before the source transaction commits. This reduces the amount of data that needs to be transmitted over the network, as changes are replicated in smaller, more frequent batches rather than waiting for complete transaction gathering.
4Reliability
If transactions are applied after commitment, then rollback costs are minimized, but replication time is extended
Solution Approach 1:
The system applies changes to the target database before the source transaction is fully committed, performing the replication action in advance. This reduces the total replication time by overlapping the replication process with the source transaction execution, while rollback costs are managed through proper transaction coordination and undo mechanisms.
Data Source
AI summary
The present disclosure relates to a method for data synchronization between a source database system and target database system, wherein execution of a database transaction of the source database system is complete if a processing step followed by an application step of the database transaction is performed. For each identified database transaction, a processing step and/or application step may be performed.