Remote Data Caching for Low Velocity Query Latency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional database management systems face inefficiencies when interacting with remote data sources due to their slower responsiveness compared to local data servers, particularly when handling large datasets.

Innovation Solution

Implementing a process that utilizes remote caching by generating a cache name based on the query and checking for the existence and validity of a cache in the remote data source, allowing for faster data retrieval by reading from the cache instead of executing a database query, if the cache is valid and not too aged.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is stored in remote data sources, then data capacity is increased, but data access speed deteriorates

Engineering Contradiction:

Improvedata capacityVSAvoiddata access speed

Core Design Contradiction:

Quantity of substanceVSSpeed

Solution Approach 1:

The patent pre-loads frequently accessed remote data into local cache memory before it is actually needed. The system monitors query patterns and proactively caches remote data sources in local volatile memory, so that when a query arrives, the data is already available locally, eliminating the slow remote access latency while maintaining the ability to store large remote datasets.

Inventive Principle:

Principle #10Preliminary action

2Speed

If data is stored in local memory, then data access speed is improved, but system cost increases

Engineering Contradiction:

Improvedata access speedVSAvoidsystem cost

Core Design Contradiction:

SpeedVSUse of energy by stationary object

Solution Approach 1:

The patent implements selective caching where only specific remote data sources that are frequently queried are loaded into expensive local volatile memory. The system analyzes query patterns and identifies which remote data sources benefit most from local caching, caching only those while leaving other remote data in the cheaper remote storage, thus optimizing the balance between access speed and memory cost.

Inventive Principle:

Principle #3Local quality

3Loss of time

If remote caching is implemented, then data retrieval time is reduced, but system complexity increases

Engineering Contradiction:

Improvedata retrieval timeVSAvoidsystem complexity

Core Design Contradiction:

Loss of timeVSDevice complexity

Solution Approach 1:

The patent implements an automated cache management system that monitors query patterns, automatically identifies which remote data sources should be cached, and dynamically loads/unloads data from local memory based on usage patterns. The system self-adjusts the cache configuration without requiring manual intervention, reducing the operational complexity despite the added architectural complexity of the caching layer.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS9037752B1Remote materialization of low velocity data

Publication Date: 2015.05.19 SAP SE

AI summary

A system includes reception of a client query identifying data stored by a remote data source, generation of a remote query of the remote data source based on the client query, determination of a cache name based on the remote query, determination of whether the remote data source comprises a cache associated with the cache name and, if it is determined that the remote data source comprises a valid cache associated with the cache name, instruction of the remote data source to read the data of the cache, and reception of the data of the cache from the remote data source.