Journal-Aware Cache Manager for Non-Relational Database Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The duplication of data in both the write-ahead-log and volatile cache memory in computer systems using non-relational databases leads to inefficiencies and reduces the hit-rate of the volatile cache memory.
Innovation Solution
An intelligent journal-aware caching manager is implemented to prevent data duplication by maintaining a first-in-first-out policy for the write-ahead-log and using an alternate caching policy for non-journaled data, along with a Least Recently Used list to manage cache entries and ensure data is not duplicated between the write-ahead-log and volatile cache memory.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored in both write-ahead-log and volatile cache memory, then data integrity is maintained, but cache hit-rate decreases and storage efficiency deteriorates
Solution Approach 1:
The patent segments data storage into distinct categories: journaled data stored only in the write-ahead-log and non-journaled data stored in the volatile cache memory. This segmentation allows the system to maintain data integrity for critical operations while optimizing cache performance for frequently accessed data that doesn't require journaling, thereby resolving the contradiction between reliability and productivity.
Solution Approach 2:
The patent implements dynamic cache management by adjusting caching behavior based on the journaling status of data. The cache manager dynamically determines whether to cache data based on whether it is journaled or non-journaled, allowing the system to adapt its storage strategy in real-time to balance data integrity requirements with cache hit-rate optimization.
2Reliability
If data is stored in both write-ahead-log and volatile cache memory, then data availability is improved, but storage space efficiency deteriorates
Solution Approach 1:
The patent segments storage space utilization based on data characteristics: journaled data occupies only the write-ahead-log space while non-journaled data utilizes volatile cache memory space. This segmentation eliminates redundant storage of the same data in both locations, improving storage space efficiency while maintaining data availability through appropriate placement in the correct storage medium.
3Speed
If volatile cache memory is used to improve read performance, then access speed increases, but cache efficiency decreases due to duplication
Solution Approach 1:
The patent applies local quality by treating journaled and non-journaled data differently in the cache management strategy. Non-journaled data receives caching optimization for fast access, while journaled data is excluded from caching to avoid duplication. This localized differentiation allows the system to maximize read performance for appropriate data types while maintaining cache efficiency.
Data Source
AI summary
An intelligent journal-aware caching manager for journaled data is provided. The caching manager ensures that data is not duplicated in a write-ahead-log (“journal”) and volatile cache memory (“cache”). The caching manager maintains first-in-first-out (“FIFO”) policy for the journal as needed and includes an alternate caching policy for non-journaled data.