Central Database Subsystem Selective Result Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed database systems face inefficiencies in network utilization and memory usage due to the processing of database requests across multiple nodes, leading to suboptimal performance and increased network traffic.
Innovation Solution
A method is introduced where a central database subsystem receives unique identifiers for database results stored by local subsystems, retrieves and processes these results, and stores them persistently, optimizing memory and network utilization by only transmitting selected results and temporarily storing data for deletion after a given period.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If database requests are processed at various nodes of distributed database systems, then processing capability is improved, but network traffic and memory usage increase
Solution Approach 1:
The patent extracts only the necessary database results from local subsystems based on unique identifiers received in second database requests, rather than transmitting all results. This selective extraction reduces network traffic while maintaining processing capability across distributed nodes.
Solution Approach 2:
The system segments database results into those that need to be transmitted to the central subsystem and those that can remain local. By dividing the data transmission task into selective segments based on request patterns, the system reduces overall network traffic while preserving distributed processing benefits.
2Speed
If database results are stored at local subsystems, then processing speed is improved, but memory utilization efficiency decreases
Solution Approach 1:
The system implements periodic deletion of stored database results from local subsystems after a given time period. This periodic cleanup maintains processing speed by keeping recent results locally available while reducing memory usage by removing older results that are less likely to be requested again.
Solution Approach 2:
The patent applies local quality by storing database results with different retention characteristics based on their likelihood of being requested. Frequently accessed results are maintained locally longer, while less frequently accessed results are deleted sooner, optimizing the balance between processing speed and memory utilization.
3Reliability
If all database results are transmitted to central subsystem, then data availability is improved, but network traffic increases
Solution Approach 1:
The system transmits only the partial set of database results that are actually needed by the central subsystem, identified through unique identifiers in processed requests. This partial action approach ensures data availability for requested results while avoiding the excessive network traffic of transmitting all results.
Solution Approach 2:
Local subsystems autonomously determine which database results to retain and which to delete based on the unique identifiers received in requests. This self-service mechanism ensures that necessary data remains available locally for quick retrieval while reducing the burden on network transmission.
Data Source
AI summary
Database requests are processed in a distributed database system comprising a central database subsystem and a plurality of local database subsystems comprising a first local database subsystem. The central database subsystem receives a second database request indicating at least one unique identifier of at least one database result of a plurality of database results which have been stored with corresponding unique identifiers by the first local database subsystem in response to a first database request received at the first local database subsystem. The at least one database result identified by the at least one unique identifier is retrieved from the first local database subsystem, processed and stored persistently in a database of the central database subsystem. At least the first local database subsystem and the central database subsystem may operate according to the New Distribution Capability (NDC) standard.