Database Cache Synchronization via Event-Triggered Metadata Propagation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cache systems face inefficiencies due to outdated data, leading to increased resource consumption and latency, as they either refresh data too frequently or infrequently, and inconsistencies in caching logic across applications complicate data management.

Innovation Solution

A system dynamically propagates data from a database to a cache by using metadata to identify updated records, maintaining accurate data in real-time, and adjusting cache architecture to optimize data storage and retrieval, thereby reducing unnecessary requests to the database and eliminating inconsistencies in caching logic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cache systems refresh data frequently to maintain data accuracy, then data consistency is improved, but resource consumption and latency increase

Engineering Contradiction:
Improvedata consistencyVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system implements periodic action by using triggers that activate cache refresh operations only when specific events occur (data updates in the database), rather than continuously or at fixed intervals. This event-driven periodic action ensures data consistency is maintained while avoiding unnecessary resource consumption during periods when no data changes occur.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The cache system performs self-service through automatic trigger-based refresh mechanisms that monitor database changes and autonomously update cache contents without requiring manual intervention or continuous external management. This self-service capability maintains data consistency while optimizing resource usage by acting only when necessary.

Inventive Principle:
Principle #25Self-service

2Reliability

If cache systems refresh data frequently to maintain data accuracy, then data consistency is improved, but latency increases

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

Solution Approach 1:

The system uses event-triggered periodic actions that refresh cache data only when database updates occur, eliminating continuous polling and reducing latency. The trigger mechanism ensures cache is updated at the precise moment data changes, maintaining consistency without the time loss associated with frequent scheduled refreshes.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system implements preliminary action by pre-establishing trigger connections between the database and cache system. When data is updated in the database, the trigger automatically initiates the cache refresh process immediately, ensuring data consistency is maintained without the latency of detecting and responding to changes after they occur.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If different applications implement their own caching logic to optimize performance, then application-specific performance is improved, but system complexity increases

Engineering Contradiction:
Improveapplication performanceVSAvoidcaching logic complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements universality by creating a standardized trigger-based caching interface that can be applied across multiple applications and data types. The same trigger mechanism and cache refresh logic work universally for different applications, eliminating the need for each application to implement its own custom caching logic while still allowing application-specific performance optimization through the unified interface.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The trigger mechanism serves as an intermediary layer between the database and various applications' cache systems. This intermediary standardizes the data synchronization process, allowing applications to benefit from optimized caching without directly implementing complex caching logic, thereby reducing overall system complexity while maintaining application-specific performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Use of energy by moving object

If cache stores data for longer periods to reduce database requests, then resource consumption is reduced, but data accuracy deteriorates

Engineering Contradiction:
Improveresource consumptionVSAvoiddata accuracy
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The system uses periodic event-triggered actions that refresh cache data at the moment database updates occur. This allows the cache to store data for extended periods between updates, reducing resource consumption, while the trigger mechanism ensures data accuracy is restored immediately when changes occur, eliminating the trade-off between cache duration and data accuracy.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS11782927B2Electronic system for dynamically propagating data from a database to a cache
Publication Date: 2023.10.10 BANK OF AMERICA CORP
  • US11782927B2 patent drawing
  • US11782927B2 patent drawing
  • US11782927B2 patent drawing

AI summary

Systems, computer program products, and methods are described herein for dynamically propagating data from a database to a cache. The present invention may be configured to receive metadata associated with updates to data records of a database, obtain, from the database and based on the metadata, the data records that have been updated, and provide the data records that have been updated to a cache. The present invention may be configured to receive, from applications, calls for the data records, obtain, from the cache and based on receiving the calls, the data records, and provide, to the applications, the data records. In some embodiments, the present invention may be configured to monitor the database and generate the metadata associated with the updates to the data records.