Tiered Cache System with Listeners for Transactional Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current caching systems face challenges in efficiently managing mutable objects and maintaining transactional consistency across distributed environments, particularly in handling complex event processing and ensuring data integrity with mutable states and relations.

Innovation Solution

A caching system that supports tiered and distributed caching with features like transactional management, mutable object handling, and advanced cache configurations, including self-loading caches, partitioned caches, and strong consistency mechanisms, to manage complex event processing and ensure data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a cache system is implemented to reduce database access, then performance is improved, but maintaining transactional consistency and data integrity becomes more complex

Engineering Contradiction:
ImproveperformanceVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The cache system is divided into multiple tiers (first cache and second cache) with different characteristics. The first cache provides fast access for frequently used data, while the second cache stores larger volumes of data. This segmentation allows the system to achieve high performance for common operations while maintaining data integrity through coordinated updates across tiers.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary mechanisms including listeners that monitor cache events and forward strategies that coordinate updates between cache tiers. These intermediaries ensure transactional consistency by propagating changes appropriately while maintaining the performance benefits of caching, thus resolving the contradiction between speed and consistency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If distributed caching is used to handle complex event processing, then scalability is improved, but ensuring data integrity across distributed environments becomes more difficult

Engineering Contradiction:
ImprovescalabilityVSAvoiddata integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system employs listeners that provide feedback mechanisms to monitor and respond to cache events across distributed environments. These listeners ensure data integrity by detecting changes, validating data, and coordinating updates across multiple cache instances, enabling scalable distributed caching while maintaining reliability.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The forward strategy mechanism ensures equipotentiality by propagating updates uniformly across all cache tiers and distributed instances. This approach maintains data consistency across the distributed system by ensuring all nodes receive and apply updates in a coordinated manner, thus achieving both scalability and data integrity.

Inventive Principle:
Principle #12Equipotentiality

3Speed

If mutable objects are cached to improve performance, then access speed is improved, but handling mutations and maintaining consistency becomes more complex

Engineering Contradiction:
Improveaccess speedVSAvoidmutation handling complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-loading data into the cache and pre-establishing listener mechanisms before mutations occur. This allows mutable objects to be accessed quickly from cache while the listener infrastructure is already in place to handle mutations, thus achieving both fast access and manageable mutation handling.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Listeners act as intermediaries between mutable cache objects and the rest of the system. These listeners monitor mutations, validate changes, and coordinate updates across cache tiers, thereby simplifying the complexity of handling mutable objects while maintaining their performance advantages.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8700855B2System and method for supporting a tiered cache
Publication Date: 2014.04.15 ORACLE INT CORP
  • US8700855B2 patent drawing
  • US8700855B2 patent drawing
  • US8700855B2 patent drawing

AI summary

A computer-implemented method and system can support a tiered cache, which includes a first cache and a second cache. The first cache operates to receive a request to at least one of update and query the tiered cache; and the second cache operates to perform at least one of an updating operation and a querying operation with respect to the request via at least one of a forward strategy and a listening scheme.