Web Application Caching Mechanism for Data Validity Arbitration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current caching mechanisms in web applications are time-based and do not guarantee the validity of data, which is a concern for enterprise systems that rely on live data.

Innovation Solution

A caching mechanism that utilizes the business logic of a web application to determine the validity of cached data through data validity arbiters, ensuring that only valid data is served to users and updating the cache with fresh data when necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If time-based caching mechanisms are used to store data locally, then performance is improved by reducing access time to data stores, but data validity cannot be guaranteed for enterprise applications that require live data

Engineering Contradiction:
Improvedata access timeVSAvoiddata validity
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where data validity arbiters continuously monitor and verify the validity of cached data using business logic. When data becomes invalid according to business rules, the system automatically detects this through validation queries and refreshes the cached data, creating a closed-loop feedback system that maintains data reliability while preserving caching benefits

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces data validity arbiters as intermediary components that mediate between the cached data and the application. These arbiters use business logic to determine data validity and act as a gatekeeper, allowing applications to access cached data only when validated, thus ensuring reliability without sacrificing the performance advantages of caching

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If cached data is used to improve performance, then access speed is increased, but the complexity of managing data validity increases

Engineering Contradiction:
Improvedata access speedVSAvoidcaching mechanism complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent segments the caching mechanism into distinct modular components: the cache storage layer, the data validity arbiter layer with business logic, and the data access layer. This segmentation allows each component to be independently managed and maintained, reducing overall system complexity while enabling sophisticated validity checking through specialized arbiter modules

Inventive Principle:
Principle #1Segmentation

3Reliability

If data is frequently refreshed from large data stores to ensure validity, then data accuracy is maintained, but performance penalties increase due to repeated access to large data stores

Engineering Contradiction:
Improvedata accuracyVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by having data validity arbiters perform selective validation only on specific cached data elements that are actually requested by applications. Instead of refreshing entire data sets, the system validates and refreshes only the necessary portions, maintaining data accuracy while minimizing the performance impact of validation operations

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9942346B2Caching mechanism for determining validity of cached data using web application business logic
Publication Date: 2018.04.10 RED HAT INC
  • US9942346B2 patent drawing
  • US9942346B2 patent drawing
  • US9942346B2 patent drawing

AI summary

Systems and methods are provided for a caching mechanism that determines validity of cached data using web application business logic. An example system includes a web container that receives a first request to return one or more generated data located in a data cache, and a web application including one or more data validity arbiters and business logic determining the validity of the one or more generated data. The system may further include a business logic caching mechanism that requests the validity of the one or more generated data from the one or more data validity arbiters, wherein the one or more data validity arbiters utilize the business logic to determine the validity of the one or more generated data.