Document Synchronization Queue Time Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Duplicate or redundant transactions occur during document synchronization between a source and target repository due to synchronization latency, leading to inefficiencies and resource wastage.
Innovation Solution
Implementing time-based identifiers, such as last processed time and queue time identifiers, to compare the processing status of transactions in the synchronization queue, ensuring only non-redundant transactions are processed and synchronized to the target repository.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If documents are continuously monitored and synchronized to the target repository, then the target repository remains up-to-date with the source repository, but redundant transactions are processed multiple times due to synchronization latency
Solution Approach 1:
The system performs preliminary actions by storing time-based identifiers (last processed time, queue time) for each transaction in the synchronization queue before processing occurs. When a transaction is encountered during processing, the system checks these pre-stored timestamps to determine if the transaction is redundant, allowing for efficient filtering before actual synchronization operations are performed.
2Reliability
If multiple transactions pertaining to the same document are processed sequentially, then all changes are synchronized, but system resources are wasted on redundant transactions
Solution Approach 1:
The system implements feedback by continuously monitoring the timestamps of transactions in the synchronization queue and comparing them against previously processed transaction timestamps. This feedback mechanism allows the system to identify and eliminate redundant transactions that would otherwise consume system resources, while ensuring that all necessary changes are still synchronized to maintain data completeness.
Data Source
AI summary
Methods for synchronizing a source document repository with a target document repository include monitoring documents of the source document repository to detect changes to the documents. A last processed time is stored in association each changed document that indicates a time when the document was last processed. A transaction item is added to a synchronization queue each time a document is changed, and a queue time is stored in association with each of the transaction items that indicates when the transaction item was added to the queue. The transaction items are processed by comparing the queue time of the transaction item with the last processed time of the document pertaining to the transaction item. If the queue time is earlier than the last processed time, the transaction item is ignored.