Local Database Replication for Client Application Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Client applications in client-server architectures face latency and high network traffic due to reliance on remote database access, and existing data caching methods struggle with determining data freshness, leading to inefficient data updates and re-downloading issues when database structures change.

Innovation Solution

Implementing a local replication of the remote database on the client device during installation, with mechanisms for synchronization and automatic data refresh, allowing the client application to maintain a synchronized local database structure and content, and using scripts to update the database schema without data loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data is cached locally on the client device, then access speed and responsiveness are improved, but data freshness and synchronization with the remote server deteriorate

Engineering Contradiction:
Improvedata access speedVSAvoiddata freshness
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-packaging data on the remote server before client requests. Data is prepared in advance and made available for immediate download, eliminating the need for client-side caching while ensuring fast access to fresh data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention extracts the data packaging and preparation function from the client device and relocates it to the remote server. The server pre-packages data according to predicted client needs, transferring only necessary data portions to the client, thus eliminating caching requirements while maintaining fast access.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If the client application requests initial data from the remote server, then data freshness is ensured, but network traffic and response time increase

Engineering Contradiction:
Improvedata freshnessVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Data is pre-packaged on the remote server in advance based on predicted client requirements. When a client installs or requests data, the pre-prepared data packages are immediately available for transfer, eliminating the time-consuming process of generating and transmitting data on-demand.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The data is segmented into logical packages or units that can be independently prepared and transferred. This allows the server to organize data into manageable chunks that can be efficiently transmitted to multiple clients simultaneously, reducing overall network traffic and response time.

Inventive Principle:
Principle #1Segmentation

3Reliability

If the database structure is updated on the remote server, then data structure currentness is improved, but client data stores must be updated causing data loss and requiring re-downloading

Engineering Contradiction:
Improvedatabase structure currentnessVSAvoidcached data loss
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The invention extracts the database structure update function from the client device and centralizes it on the remote server. The server maintains the authoritative database structure and manages all update operations, allowing clients to receive structure updates without losing their local data through intelligent synchronization.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of requiring clients to maintain exact copies of the database structure, the system uses a copy-based approach where the server maintains the master structure definition. Clients receive structure updates as separate metadata or configuration files that describe how to interpret their existing data, preserving local data while ensuring structure currentness.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9116892B2Method for improving the responsiveness of a client device
Publication Date: 2015.08.25 LEMON INC(GB)
  • US9116892B2 patent drawing
  • US9116892B2 patent drawing
  • US9116892B2 patent drawing

AI summary

A method for improving the responsiveness of a client application by providing that application with a local database which is a replicated subset of a database held on a remote server.