Staging Layer Cache for Automatic Data Discovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data access and caching systems face performance issues due to increasing data usage, leading to slowdowns and increased total cost of ownership, as they require recalibration and resizing of clients and databases, and fail to efficiently manage dependencies between database expertise and performance optimization.

Innovation Solution

A computer-implemented method and system that utilizes a staging layer with a cache to determine the completeness of requested information, retrieving only necessary data from an underlying database layer, merging partial cache data, and updating the cache with push notifications to optimize data access and reduce the load on the database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data usage increases over time, then more data can be accessed and analyzed, but performance slows down and total cost of ownership increases

Engineering Contradiction:
Improvedata usageVSAvoidperformance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The system segments data into cached data and non-cached data, separating frequently accessed data from the main database. The cache stores a subset of information from the underlying database layer, allowing the system to handle increasing data usage without proportionally increasing database load, thus maintaining performance while supporting greater data quantities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-caching data that is likely to be requested based on usage patterns. The automated data discovery component identifies frequently accessed data and caches it in advance, so when data usage increases, the performance impact is minimized because the data is already available in the cache rather than requiring additional database queries.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If data usage increases over time, then more data can be accessed and analyzed, but total cost of ownership increases due to recalibration and resizing requirements

Engineering Contradiction:
Improvedata usageVSAvoidtotal cost of ownership
Core Design Contradiction:
Quantity of substanceVSEase of manufacture

Solution Approach 1:

The system implements self-service through automated data discovery and automated cache management. The system automatically identifies usage patterns, determines which data to cache, and manages cache contents without requiring manual recalibration or resizing operations. This automation reduces the total cost of ownership by eliminating the need for expert database intervention as data usage grows.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes parameters dynamically by adjusting cache size and content based on observed usage patterns rather than requiring fixed, pre-determined configurations. The automated discovery mechanism monitors data access patterns and adjusts the cached data subset accordingly, allowing the system to adapt to increasing data usage without manual recalibration or expensive resizing operations.

Inventive Principle:
Principle #35Parameter changes

3Speed

If a cache stores only a subset of information, then data access speed improves for cached data, but completeness of cached information decreases

Engineering Contradiction:
Improvedata access speedVSAvoidcompleteness of cached information
Core Design Contradiction:
SpeedVSLoss of information

Solution Approach 1:

The cache is dynamic rather than static. The system continuously monitors data usage patterns and automatically adjusts which data remains in the cache and which is evicted. This dynamic approach ensures that the cache maintains the most relevant data for current usage patterns, optimizing both access speed for frequently requested data and completeness by adapting to changing information needs over time.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where data access patterns are monitored and fed back into the cache management process. The automated data discovery component uses this feedback to determine which data should be cached and which should be removed, ensuring that the cache maintains optimal completeness for current usage patterns while preserving fast access speeds for frequently requested information.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11074267B2Staged approach to automatic data discovery and performance
Publication Date: 2021.07.27 SAP SE
  • US11074267B2 patent drawing
  • US11074267B2 patent drawing
  • US11074267B2 patent drawing

AI summary

The disclosure generally describes methods, software, and systems, including a method for caching information. A request for information is received at a staging layer. A determination is made whether the requested information already exists entirely in a cache. In response to determining that the requested information does not exist entirely in the cache, at least some of the requested information from the underlying database layer is retrieved. A completeness level to which the requested information exists in the cache is determined. In response to determining that the requested information exists partially in the cache, cache-nonresident information is retrieved from the underlying database layer and merged with information in the cache. In response to determining that none of the requested information exists in the cache, the request is forwarded to the underlying database layer. The requested information is provided by the staging layer to a presentation layer.