Asynchronous Deletion in Non-Relational Databases via Association Indexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-relational databases face increased latency and resource overhead due to the need to search through entire data entry lists for deleted records, which hampers performance and efficiency during deletion operations.
Innovation Solution
Implementing asynchronous deletion in non-relational databases by storing associations between data entries and primary key indices, allowing for the deletion of associations only when a read request is received, thereby reducing the need for frequent data lookups and minimizing processing resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If synchronous deletion is performed in non-relational databases, then data consistency is maintained, but database latency increases and processing overhead increases
Solution Approach 1:
The patent applies preliminary action by pre-storing associations between data entries and primary key indices in a separate data structure. This allows the database to quickly identify and delete only relevant associations during deletion operations, rather than searching through entire data entry lists, thus reducing latency while maintaining consistency.
Solution Approach 2:
The patent introduces an intermediary data structure that stores mappings between data entries and primary key indices. This intermediary layer acts as a mediator between the data entries and the index, enabling efficient deletion operations by providing a direct path to identify affected associations without scanning all data entries.
2Reliability
If synchronous deletion is performed in non-relational databases, then data consistency is maintained, but resource overhead increases
Solution Approach 1:
By pre-storing associations in a dedicated data structure during data insertion, the system prepares the groundwork for efficient deletion. This preliminary action reduces the computational burden during deletion operations, lowering processing overhead and energy consumption while ensuring data consistency through targeted updates.
Solution Approach 2:
The intermediary association storage structure reduces processing overhead by providing a direct mapping mechanism. Instead of scanning all data entries to find associations during deletion, the system uses this intermediary structure to quickly identify and update only the necessary associations, significantly reducing computational resources required.
3Speed
If data associations are stored in non-relational database, then single index searching is optimized, but deletion operations require extensive searches
Solution Approach 1:
The patent segments the storage of associations from the main data entries by maintaining a separate data structure that stores associations between data entries and primary key indices. This segmentation allows independent optimization: data entries can be searched efficiently through the single index, while deletions can quickly identify affected associations through the separate association structure without scanning all entries.
Solution Approach 2:
The separate association storage structure serves as an intermediary that bridges data entries and primary key indices. This intermediary enables fast deletion operations by providing direct access to associations without requiring extensive searches through the entire dataset, thus resolving the contradiction between optimized searching and efficient deletion.
Data Source
AI summary
Methods, systems, and devices for asynchronous deletion at a non-relational database are described. The non-relational database may store a set of data object associations. The non-relational database may receive a read request indicating a first data object identifier. Based on the first data object identifier indicated in the read request, the non-relational database may identify a second data object identifier according to a first data object association of the stored set of data object associations that is indexed in the non-relational database with the first data object identifier. The non-relational database may determine that a last data entry that is indexed in the non-relational database with the identified second data object identifier and is associated with the first data object identifier has been deleted from the non-relational database. The non-relational database may delete the first data object association from the non-relational database.


