Business Logic Agent Cache Fill Buffering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional content delivery systems face challenges in efficiently managing caching, particularly when a cache lock is enabled during cache filling, leading to delays in servicing additional requests for the same content.
Innovation Solution
The implementation of a business logic agent that maintains a copy of content data in its cache storage, allowing it to service additional requests while the caching agent's cache is being filled, thereby acting as an intelligent fill-buffering proxy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a cache lock is enabled during cache filling to ensure data consistency, then reliability is improved, but additional requests for the same content must wait for cache fill completion, worsening latency and productivity
Solution Approach 1:
The business logic agent performs preliminary action by filling its own cache storage with the content data before the caching agent's cache is filled. This allows the business logic agent to immediately service additional requests from its cache, eliminating the waiting time that would otherwise occur while the caching agent's cache fill completes, thus resolving the contradiction between maintaining data consistency through cache locking and reducing request latency
Solution Approach 2:
The business logic agent acts as an intermediary between the caching agent and the origin server. It receives content data from the upstream node (origin server or another CDN node) and maintains a local copy in its cache storage, enabling it to service requests independently of the caching agent's cache fill status. This intermediary role allows the system to maintain reliability while reducing latency by providing an additional data source
2Reliability
If additional requests wait for cache fill completion, then data consistency is maintained, but bandwidth is wasted by requiring direct connections to the origin server
Solution Approach 1:
The business logic agent performs preliminary action by pre-filling its cache storage with the content data before the caching agent's cache fill completes. This preliminary caching enables the business logic agent to service additional requests from its local cache, preventing these requests from needing to connect directly to the origin server and thus reducing unnecessary bandwidth consumption while maintaining data consistency
Solution Approach 2:
The business logic agent creates a copy of the content data in its own cache storage, separate from the caching agent's cache. This copying mechanism provides an additional data source that can service requests without requiring direct origin server connections, thereby reducing bandwidth usage while ensuring data availability and consistency through the replicated copy
Data Source
AI summary
Examples described herein relate to apparatuses and methods for managing caching for a content delivery system, which may include receiving a content request indicating that the caching agent is requesting content data for a client, filling the content data in a first cache storage of the business logic agent, providing the cached content data to the caching agent, and while a second cache storage of the caching agent is being filled with the content data, maintaining the cached content data in response to receiving additional content requests from the caching agent. The additional content requests may indicate that the caching agent is requesting the same content data for additional clients.