Edge-Cached Meta-Data Injection for Dynamic Web Content
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional edge caching solutions fail to efficiently cache and serve dynamic web content due to frequent cache updates and inability to conditionally react to events, leading to slower page rendering, increased cache data, and higher operational costs.
Innovation Solution
The system dynamically injects meta-data and meta-functions around view components on a web page, allowing conditional reactions and machine learning feedback loops without impacting cacheability, by generating unique IDs and using edge-side include (ESI) directives to wrap components with necessary instructions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If dynamic web content is cached at CDN edge, then page rendering speed is improved, but cache update frequency increases and caching efficiency deteriorates
Solution Approach 1:
The patent segments web page content into static and dynamic components, caching only the static portions at CDN edge while leaving dynamic content to be generated on-demand. This is achieved through wrapper injection that identifies and isolates dynamic view components, allowing the static wrapper structure to be cached independently without being invalidated by dynamic content changes.
Solution Approach 2:
The patent extracts dynamic content from the cached page structure by using wrapper injection to identify and remove dynamic view components before caching. The extracted dynamic content is then regenerated on-demand from the cached static wrapper, eliminating the need to cache-update dynamic portions while maintaining the ability to serve static content from cache.
2Quantity of substance
If conventional edge caching is used for dynamic content, then cache data volume increases, but operational costs increase
Solution Approach 1:
By segmenting content into cacheable static wrappers and non-cacheable dynamic components, the system reduces the total cache data volume stored at CDN edge. Only the static wrapper structures are cached, not the entire dynamic content, which reduces cache storage requirements and associated operational costs.
Solution Approach 2:
The patent discards dynamic content from the cached version and recovers it on-demand through template rendering using cached data. Instead of storing and updating dynamic content in cache, the system discards it after serving and recovers it fresh for each dynamic request, reducing cache data volume and update overhead.
3Loss of energy
If dynamic content is served from CDN, then traffic cost is reduced, but ability to react to events conditionally deteriorates
Solution Approach 1:
The patent introduces an intermediary layer between the cached static content and the user agent: a client-side JavaScript runtime that executes cached JavaScript code. This intermediary enables conditional logic and event handling in the browser while the static wrapper structure remains cached at CDN, allowing traffic cost reduction without sacrificing adaptability.
Solution Approach 2:
The system enables self-service by caching JavaScript code that runs in the user agent to generate dynamic content on-client-side. The cached JavaScript autonomously handles event conditioning and dynamic content generation without requiring server-side cache updates, reducing traffic costs while maintaining conditional reaction capabilities.
Data Source
AI summary
Systems and techniques for dynamic generation and injection of edge-cached meta-data are described herein. A request for a component of a web page requested by a user from a content delivery network may be received. The component may be retrieved from an application server. Instructions may be generated for the component. The instructions may be injected around the component may be wrapped to form a wrapped component. The wrapped component may be transmitted to the content delivery network for storage in an edge cache.