Hybrid Database Structure for Real-Time Document Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Relational databases face challenges in managing and updating large volumes of electronic documents efficiently, particularly in cloud-based systems, due to computational complexity and delays in propagating data updates, leading to outdated information and user frustration.
Innovation Solution
A hybrid database structure combining relational and non-relational databases, where relational databases store documents and entity identifiers, and non-relational graph databases manage entity associations and category relationships, enabling real-time updates and filtering of documents through entity and category associations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If relational databases are used to store and manage large volumes of electronic documents, then data consistency and structured organization are improved, but computational complexity and update propagation time increase
Solution Approach 1:
The patent segments the database system into two distinct components: a relational database for storing documents and maintaining data consistency, and a separate non-relational graph database for managing entity associations and category relationships. This segmentation allows each database type to optimize for its specific function, reducing the computational burden on the relational database during updates and eliminating the need for complex recomputations across the entire system.
Solution Approach 2:
The non-relational graph database acts as an intermediary layer between the relational database and the user interface. It handles the complex computations for entity associations and category relationships, storing pre-computed data that can be quickly retrieved and displayed. This intermediary absorbs the computational complexity, allowing the relational database to maintain consistency without bearing the full burden of real-time update propagation.
2Measurement precision
If complex computations are performed to update database sections in real-time, then data accuracy is improved, but system performance and user responsiveness deteriorate
Solution Approach 1:
The system performs computations in advance by maintaining a separate graph database that stores pre-computed entity associations and category relationships. When documents are added, removed, or modified in the relational database, the corresponding changes in entity associations are pre-calculated and stored in the graph database. This preliminary action ensures data accuracy is maintained while avoiding the need for complex computations at the moment of user interaction, thus preserving system performance.
3Adaptability or versatility
If documents are stored in multiple locations for easy access, then document availability is improved, but the number of documents to be sorted and managed increases
Solution Approach 1:
The graph database serves as an intermediary that manages the complexity of multiple document locations. It stores entity associations that track which documents are associated with which entities and categories across multiple locations. When users need to retrieve documents, they query the graph database for entity associations, which efficiently returns the relevant documents without requiring users to manually sort through or navigate complex folder structures. This intermediary layer handles the sorting and management complexity internally.
4Ease of operation
If cloud-based processing is used for remote document management, then accessibility is improved, but update propagation delays increase
Solution Approach 1:
The patent segments the data storage and computation functions in the cloud-based system. The relational database stores documents and basic metadata, while the separate graph database stores pre-computed entity associations and category relationships. This segmentation allows the system to serve documents quickly from the relational database while using the graph database to provide pre-computed association data, reducing the need for complex real-time computations over the network and minimizing update propagation delays for users accessing the system remotely.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods, systems and computer program products for organizing and displaying in real-time data related to a plurality of documents. A plurality of documents and a plurality of entity identifiers are stored in a relational database storage. Each entity identifier has an entity type selected from a plurality of entity types. A plurality of entity associations between the plurality of entity identifiers and the plurality of documents are stored in a non-relational database storage. Each entity association defines a relationship between one or more entity identifiers and a selected document in the plurality of documents. A plurality of file icons are displayed in a display interface. The plurality of file icons includes active icons corresponding to a election of the plurality of documents where the selection is determined by querying he non-relational database storage using at least one currently-selected entity identifier.