Database Query Cache Validation for Response Time

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems face challenges in minimizing response times for complex database requests without compromising the accuracy and validity of the returned data, as they often rely on caching mechanisms that may provide outdated results and increase computational costs.

Innovation Solution

A database system that utilizes a cache to quickly return initial query results and validates subsequent queries by retrieving current data from the database, ensuring data validity while reducing overall response time by minimizing direct database queries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If caching mechanisms are used to reduce response times, then response time is improved, but data accuracy and validity deteriorate due to outdated cached results

Engineering Contradiction:
Improveresponse timeVSAvoiddata accuracy
Core Design Contradiction:
Loss of timeVSMeasurement precision

Solution Approach 1:

The system performs preliminary validation by checking whether subsequent queries relate to previously cached queries. When a relationship is detected, the system proactively validates the cached data against current database results before returning, ensuring data accuracy is maintained while still leveraging the cache for speed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the validity of cached data is continuously checked against current database results. When cached data is found to be outdated or inconsistent with current database state, the system updates the cached results, creating a closed-loop feedback system that maintains data accuracy while preserving caching benefits.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If direct database queries are performed for every request, then data accuracy is improved, but computational costs and response times worsen

Engineering Contradiction:
Improvedata accuracyVSAvoidcomputational efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

Instead of performing full validation for every query, the system applies partial validation only when subsequent queries are detected to relate to previous cached queries. This selective approach performs validation only when necessary, reducing unnecessary computational overhead while maintaining data accuracy for relevant queries.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system applies different processing qualities to different queries based on their relationship to cached data. Queries that relate to cached results receive enhanced validation and checking, while unrelated queries are processed normally. This local differentiation optimizes computational resources by focusing validation efforts where they are most needed.

Inventive Principle:
Principle #3Local quality

3Reliability

If cache validation is performed for all cached data, then data validity is improved, but response time and computational resources worsen

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

Solution Approach 1:

The system performs validation partially rather than completely for all cached data. It specifically targets only those cached results that are related to subsequent queries, leaving unrelated cached data unvalidated. This selective partial validation maintains data validity for relevant results while minimizing the time and computational resources spent on validation.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system extracts and validates only the specific subset of cached data that is relevant to subsequent queries, rather than validating the entire cache. By taking out only the necessary portions for validation, the system maintains data validity where needed while avoiding the performance penalty of comprehensive cache validation.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3924838B1Processing complex database querys
Publication Date: 2024.04.24 AMADEUS SAS
  • EP3924838B1 patent drawingFigure 1
  • EP3924838B1 patent drawingFigure 2
  • EP3924838B1 patent drawingFigure 3

AI summary

Multiple database queries forming a complex database request are processed. A first query and second query are answered by a first response and a second response based on a cache storing cached data. A third query which is related to the second query is answered based on a database storing current corresponding to the cached data. A selected subset of the cached data returned with the second response is validated by corresponding current data stored in the database.