Database Management Compute Device for Multithreaded Data Duplication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multithreaded environments, compute devices may simultaneously attempt to write data to a central database, leading to conflicts and duplicates, which cause confusion and processing delays for subsequent reads.
Innovation Solution
A database management compute device identifies concurrent write requests for the same data set and performs corrective actions by writing data to a secondary table designated for temporary records, thereby preventing conflicts and duplicates in the primary database table.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple compute devices execute separate threads and write data to the central database simultaneously, then productivity is improved through parallel processing, but data conflicts and duplicates occur in the database
Solution Approach 1:
The patent introduces a mediator mechanism that intercepts write requests from multiple threads, checks for potential conflicts using indexing on entity identifiers and property types, and serializes conflicting writes. This intermediary layer allows parallel processing to continue while preventing data conflicts, thus maintaining both productivity and reliability.
Solution Approach 2:
The system performs preliminary actions by constructing indexes on entity identifiers and property types before write operations occur. These indexes enable the system to predict and detect potential conflicts before they manifest as actual data issues, allowing preventive measures to be taken in advance while maintaining parallel processing capability.
2Speed
If write requests are processed concurrently without coordination, then processing speed is improved, but conflicts and duplicates cause processing delays for subsequent reads
Solution Approach 1:
The patent implements a mechanism that allows non-conflicting write requests to skip serialization overhead and be processed rapidly in parallel. By using indexes to quickly identify conflicts, the system can rush through safe writes without delay while only serializing the minimal subset of conflicting operations, thus maintaining high processing speed while avoiding delays.
Solution Approach 2:
The mediator mechanism selectively serializes only conflicting write requests while allowing non-conflicting requests to proceed in parallel. This selective approach minimizes the time loss from serialization while preventing conflicts that would cause larger delays in subsequent read operations.
3Reliability
If a secondary table is introduced to manage temporary records, then data conflict prevention is improved, but device complexity increases
Solution Approach 1:
The patent segments the database structure into a primary table for committed data and a secondary table for temporary conflict-resolution data. This segmentation isolates the complexity of conflict management to the secondary table while keeping the primary table simple and efficient for read operations, thus improving reliability without excessively increasing overall system complexity.
Solution Approach 2:
The secondary table serves as a temporary holding area for conflict-resolution data that is discarded after use. Once conflicts are resolved and data is committed to the primary table, the temporary records in the secondary table are cleaned up. This approach contains complexity temporarily during conflict resolution without permanently increasing the operational database structure.
Data Source
AI summary
Technologies for managing data duplication in a multithreaded environment include a compute device. The compute device includes circuitry configured to receive a request to write, to a primary table of a database, a data set pertaining to a property of an entity. The circuitry is also configured to construct, based on the data set, an index to determine whether a record pertaining to the property of the entity is present in the database, determine, using the constructed index, whether an existing record pertaining to the property of the entity is present in a secondary table designated to contain temporary records associated with write requests from a predefined period, and perform, in response to a determination that an existing record pertaining to the property of the entity is present in the secondary table, a corrective action to remediate concurrent writes to the database pertaining to the property of the entity.