Hybrid Caching System for Reducing Application Data Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data redundancy reduction techniques in segment caching systems are application unaware, failing to reduce application requests/responses and respective indices communicated over a network, even when redundant data is cached.
Innovation Solution
A hybrid caching system that generates application-aware indices and uses an application optimizer cache to determine availability of segment cache indices, allowing for efficient retrieval and communication of application units by either local or peer terminal devices, thereby reducing redundant data traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of substance
If data redundancy reduction techniques are used to exchange indices instead of redundant data, then the amount of redundant data communicated over the network is reduced, but application requests/responses and respective indices still need to be communicated over the network
Solution Approach 1:
The system performs preliminary actions by checking the application optimizer cache before communicating application requests over the network. The cache stores application-specific indices and segment cache indices that enable local resolution of requests without network communication, thus preventing application requests and indices from being communicated over the network in the first place
Solution Approach 2:
The application optimizer cache acts as an intermediary between the application and the segment cache/network. It stores application-specific indices that map to segment cache indices, enabling the system to resolve application requests locally without needing to communicate with other network nodes, thereby reducing both redundant data and application request traffic
2Loss of substance
If segment caching is used to store redundant data locally, then redundant data communication is reduced, but the system remains application unaware and cannot optimize application-level traffic
Solution Approach 1:
The system applies local quality by creating application-specific caches (application optimizer cache) that are tailored to each application's needs. This cache stores indices specific to particular applications, enabling the system to optimize traffic patterns for each application individually while maintaining the general segment caching infrastructure for redundant data
Solution Approach 2:
The system changes parameters by introducing application-specific indices as an additional layer of indexing. Instead of only using segment cache indices, the system now uses application-specific indices that map to segment cache indices, transforming the caching mechanism from generic to application-aware while maintaining compatibility with the underlying segment cache structure
Data Source
AI summary
A system operable to: receive a request for an application unit from a first device; generating a key for the application unit; look up segment cache indices corresponding to the application unit, according to the key; and determine whether the segment cache indices are available. Where the segment cache indices are available, the system may retrieve a segment cache using the segment cache indices; and then retrieve the application unit using the retrieved segment cache. Otherwise, where the segment cache indices are not available, the system may communicate the request to a second device to receive a response from the second device including the segment indices. Further, the system may receive the response from the second device; store a segment index sequence for the application unit in an application optimizer cache based on the response; and retrieve the application unit via the segment index sequence.