Cache Coherency Engine with Dynamic Update Thresholds

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing database cache systems fail to optimally utilize computing resources, leading to suboptimal response times and accuracy in database queries, particularly in high-volume transactional systems using command query responsibility separation (CQRS).

Innovation Solution

A cache management system that tracks the frequency of requests serviced by the database and cache, updating the cache when the database is used excessively relative to the cache, and employing predictive algorithms to anticipate future usage patterns, thereby optimizing the combined processing load.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the cache is updated frequently to maintain data accuracy, then the reliability of cached data improves, but the processing overhead and system complexity increase

Engineering Contradiction:

Improvedata accuracyVSAvoidprocessing overhead

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system dynamically changes the cache update parameter (update frequency) based on workload characteristics. When database workload exceeds cache workload beyond a threshold ratio, the system adjusts the cache update strategy to synchronize with database commits, ensuring data accuracy while adapting to varying system conditions rather than using a fixed update policy

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The system implements feedback by monitoring the ratio of database workload to cache workload and using this information to control cache update timing. The cache management system continuously evaluates whether the update threshold has been exceeded and adjusts update behavior accordingly, creating a closed-loop control system that balances data accuracy with processing overhead

Inventive Principle:

Principle #23Feedback

2Device complexity

If the cache is updated less frequently to reduce processing overhead, then the system complexity decreases, but the response time and data accuracy deteriorate

Engineering Contradiction:

Improveprocessing overheadVSAvoidresponse time

Core Design Contradiction:

Device complexityVSLoss of time

Solution Approach 1:

The system dynamically adjusts the cache update parameter based on the measured workload ratio. When the ratio indicates heavy database usage relative to cache usage, the system increases update frequency to maintain response time quality, while reducing updates during lighter workloads to minimize overhead

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The cache update mechanism transitions from a static, fixed-interval approach to a dynamic, condition-based approach. The update frequency adapts in real-time based on the relationship between database and cache workloads, allowing the system to optimize response time under varying load conditions without incurring constant maximum overhead

Inventive Principle:

Principle #15Dynamics

3Productivity

If the cache and database operate independently with separate workloads, then the productivity of each component improves, but the data coherency between them deteriorates

Engineering Contradiction:

Improveprocessing capacityVSAvoiddata coherency

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The cache update mechanism acts as an intermediary between the database and cache workloads. It monitors both workloads and mediates data synchronization by triggering cache updates from database commits when the workload ratio exceeds the threshold, maintaining coherency while allowing independent operation

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary synchronization by updating the cache proactively from database commits before cache validity issues arise. This preliminary action ensures data coherency is maintained without requiring reactive synchronization that would disrupt independent workload processing

Inventive Principle:

Principle #10Preliminary action

4Reliability

If the cache update threshold is set low to ensure data accuracy, then the reliability improves, but the processing load increases

Engineering Contradiction:

Improvedata coherencyVSAvoidprocessing load

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system dynamically changes the effective threshold based on system conditions. Rather than using a fixed low threshold that would always trigger updates, the threshold mechanism adapts to workload patterns, triggering updates only when the database-to-cache workload ratio justifies synchronization, thus balancing coherency with processing load

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS11650922B2Cache coherency engine

Publication Date: 2023.05.16 HOME DEPOT PRODUCT AUTHORITY LLC

AI summary

A method for operating a database and a cache of at least a portion of the database may include receiving a plurality of read requests to read a data entity from the database and counting respective quantities of the requests serviced from the database and from the cache. The method may further include receiving a write request to alter the data entity in the database and determining whether to update the cache to reflect the alteration to the data entity in the write request according to the quantity of the requests serviced from the database and the quantity of the requests serviced from the cache. In an embodiment, the method further includes causing the cache to be updated when a ratio of the quantity of the requests serviced from the database to the quantity of the requests serviced from the cache exceeds a predetermined threshold.