Client Database Segmentation for Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face increased latency when updating a relational database management system (RDBMS) on a client device, as update transactions hinder reference transactions and increase latency during data retrieval.
Innovation Solution
A data processing method that utilizes two client DBs, where one is designated as a reference storage area and the other as an update storage area, allowing for parallel execution of reading and writing operations without disturbing each other, thereby reducing latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If update data are written in the RDBMS on the client to automatically reflect server updates, then data consistency is improved, but reference transactions are hindered and latency increases
Solution Approach 1:
The patent divides the single RDBMS on the client into two separate databases: a first RDBMS dedicated to reference transactions and a second RDBMS dedicated to update transactions. This segmentation allows reference and update operations to proceed independently without interfering with each other, thus maintaining data consistency while preventing latency increases in reference transactions.
Solution Approach 2:
The patent introduces a switching mechanism that acts as an intermediary between the two RDBMS instances and the application. This switching mechanism manages which database is used for reference transactions and which is used for update transactions, ensuring that update operations do not block reference operations while maintaining data consistency.
2Device complexity
If a single RDBMS is used on the client for both reference and update operations, then device complexity is reduced, but reference transactions are disrupted by update operations
Solution Approach 1:
The patent segments the database system into two separate RDBMS instances on the client, with each instance dedicated to a specific type of transaction. This segmentation isolates reference transactions from update operations, preventing disruptions while maintaining manageable complexity through clear functional separation.
Solution Approach 2:
The patent implements a dynamic switching mechanism that can flexibly manage the two RDBMS instances based on transaction type. This dynamic approach allows the system to adaptively route reference transactions to the first RDBMS and update transactions to the second RDBMS, optimizing transaction efficiency while keeping the overall system structure manageable.
Data Source
AI summary
Any one of a first storage area and a second storage area, in which redundant data are respectively written, is set as a reference storage area, reference data are read in accordance with a request from the storage area set as the reference storage area between the first storage area and the second storage area, and, when update data are received from an external storage device, information based on the update data is written in the storage area not set as the reference storage area between the first storage area and the second storage area and the information based on the update data is written in the storage area set as the reference storage area.