Transaction ID Object Sync After Repository Interruptions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data synchronization methods struggle when interruptions occur, as they may lose track of transactions that have been executed on the source data repository but not on the destination, leading to inefficiencies or the inability to continue synchronization.
Innovation Solution
The system uses transaction IDs stored within data objects to identify and copy objects from the source to the destination data repository, bypassing the need to re-execute transactions that were not processed on the destination, by resuming synchronization through object copying after interruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional data synchronization methods are used, then data consistency between source and destination repositories is maintained, but the system cannot efficiently resume synchronization after interruptions occur
Solution Approach 1:
The system performs preliminary actions by embedding transaction IDs within data objects before synchronization occurs. This allows the destination repository to later identify which transactions have been applied without needing to re-execute or track them separately, enabling efficient resumption after interruptions.
Solution Approach 2:
Transaction IDs serve as an intermediary mechanism between the source and destination repositories. Instead of directly tracking synchronization state through complex transaction logs or re-execution mechanisms, the patent uses transaction IDs embedded in objects as a mediator to communicate which data has been synchronized, simplifying the resumption process.
2Reliability
If the system re-executes transactions on the destination repository to ensure consistency, then data integrity is maintained, but time is lost and productivity decreases during synchronization
Solution Approach 1:
Instead of re-executing transactions on the destination repository, the system copies transaction ID information from source objects to identify synchronization state. This copying approach maintains data integrity verification while eliminating the time-consuming re-execution process, allowing faster synchronization resumption.
Solution Approach 2:
The transaction IDs are preliminarily embedded in objects during creation or modification at the source. This preliminary tagging allows the destination to immediately identify what needs to be synchronized without needing to re-process or re-execute transactions, significantly reducing synchronization time.
3Reliability
If the system tracks all executed transactions separately to resume synchronization after interruptions, then synchronization completeness is ensured, but device complexity increases
Solution Approach 1:
The patent merges the transaction tracking information directly into the data objects themselves by embedding transaction IDs within them. This eliminates the need for separate tracking systems, logs, or metadata structures, reducing device complexity while ensuring synchronization completeness through the embedded identifiers.
Solution Approach 2:
Data objects become self-service by carrying their own transaction ID information internally. Instead of requiring an external tracking system to monitor which transactions have been synchronized, the objects themselves contain the necessary information, simplifying the overall system architecture while maintaining completeness.
Data Source
AI summary
Techniques for data synchronization using transaction identifications within objects are disclosed. In some embodiments, a method comprises the following: executing a first data synchronization process for synchronizing data objects comprising corresponding transaction identifications (IDs) from a source data repository to a destination data repository, wherein an interruption occurs in the first data synchronization process; identifying a first transaction ID for the first data synchronization process that was last processed prior to the interruption; identifying a second transaction ID that is subsequent to the first transaction ID in a sequence of transaction IDs; identifying a second set of one or more data objects that each comprise the second transaction ID; and executing a second data synchronization process for synchronizing the second set of one or more data objects by copying the second set of one or more data objects from the source data repository to the destination data repository.