Shared Cache for Enterprise Data Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In cloud-based enterprise computing environments, accessing and displaying shared data can be inefficient due to the need for multiple separate requests to servers, leading to increased processing time and resource usage, which can frustrate users and impact productivity.

Innovation Solution

Implementing a shared cache on client devices to store frequently accessed data, allowing for local retrieval without additional server requests, thereby reducing the time it takes to display information from previously viewed records and articles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple separate requests are sent to servers for accessing shared data, then data can be retrieved from the server, but processing time and resource usage increase

Engineering Contradiction:

Improvedata retrieval accuracyVSAvoidprocessing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a shared cache on client devices that pre-stores frequently accessed shared data locally. When a user needs data, the system first checks the local cache before making server requests. This preliminary action of caching data in advance eliminates the need for repeated server requests, significantly reducing processing time while maintaining data retrieval accuracy.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If multiple separate requests are sent to servers for accessing shared data, then data can be retrieved from the server, but resource usage increases

Engineering Contradiction:

Improvedata retrieval accuracyVSAvoidresource usage

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

By pre-caching shared data on client devices, the system avoids repeated server communications. The cache stores data locally so that subsequent accesses retrieve information from local memory rather than consuming network resources and server processing power, significantly reducing overall resource usage while maintaining reliable data retrieval.

Inventive Principle:

Principle #10Preliminary action

3Loss of time

If data is cached locally on client devices, then access time is reduced, but device memory is required

Engineering Contradiction:

Improveaccess timeVSAvoiddevice memory

Core Design Contradiction:

Loss of timeVSVolume of stationary object

Solution Approach 1:

The shared cache is designed to serve multiple users and multiple applications simultaneously. A single cached data set on one device can be shared across different users' sessions and various applications, maximizing the utility of the stored data. This multi-functional approach justifies the memory investment by allowing one cache to serve many purposes and many users.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The cache implementation dynamically adjusts caching strategies based on data access patterns, data size, and available memory. The system can change caching parameters such as cache capacity, eviction policies, and pre-fetching thresholds to optimize the balance between access time improvement and memory consumption, adapting to different device conditions and usage scenarios.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS11436227B2Accessing and displaying shared data

Publication Date: 2022.09.06 SALESFORCE INC

AI summary

Disclosed are examples of systems, apparatus, methods, and computer program products for accessing and displaying shared data. In some implementations, a shared cache can be maintained. A first component and a second component can be identified. A shared record can be identified as associated with the first component and the second component. It can be determined that the shared record is valid. Shared record data from the shared record can be displayed through the first component and the second component in a user interface.