Asset Merging System for Third-Party Web Content Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Third-party online systems face significant load strain and performance issues due to frequent requests for third-party assets from multiple systems, which can lead to slow web page loading and asset unavailability, especially when certain assets are filtered or blocked in certain regions.
Innovation Solution
An asset merging system generates and maintains merge files containing assets from multiple third-party systems, comparing hash values to determine changes and merging only updated assets, storing these files in content delivery networks (CDNs) geographically optimized for user regions to reduce latency and improve performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If third party systems serve assets directly to multiple online systems, then asset availability is ensured, but load strain on third party systems increases significantly
Solution Approach 1:
The patent introduces an asset merging system that acts as an intermediary between third party systems and online systems. This merging system consolidates asset requests from multiple online systems, merges assets into single bundled responses, and serves them to reduce the number of individual requests reaching third party systems, thereby reducing load strain while maintaining asset availability
Solution Approach 2:
The patent merges multiple asset requests into a single consolidated response by combining assets from different third party systems into bundled asset responses. This merging process reduces the total number of requests to third party systems and improves overall system efficiency
2Adaptability or versatility
If web pages include assets from multiple third party systems, then functionality is enhanced, but web page loading speed decreases due to reliance on the slowest third party system
Solution Approach 1:
The asset merging system performs preliminary actions by pre-fetching and merging assets from multiple third party systems before they are actually needed by the online system. This allows assets to be prepared in advance and served more quickly when requested, reducing the impact on web page loading speed
Solution Approach 2:
The patent combines multiple asset requests into a single merged response, allowing the online system to retrieve all needed assets in one operation rather than waiting for multiple separate third party systems to respond sequentially, thereby improving web page loading speed
3Reliability
If third party assets are served from original third party systems, then asset freshness is maintained, but load strain on third party systems increases
Solution Approach 1:
The asset merging system serves as an intermediary that maintains asset freshness by periodically updating assets from third party systems while consolidating requests. This allows the system to keep assets current without subjecting third party systems to continuous direct access from multiple online systems
Solution Approach 2:
The system performs preliminary asset fetching and caching, updating assets in advance before they are needed. This preliminary action maintains asset freshness while reducing the frequency and intensity of requests to third party systems
Data Source
AI summary
An asset merging system generates a merge file containing assets from multiple party systems. The asset merging system receives the assets and determines whether any of the assets has changed versus previously received versions of the assets. If any of the received assets has changed, the asset merging system generates a merge file containing at least the most recent version of the changed assets. The asset merging system then communicates the merge file to a content delivery network (CDN) for serving to users requesting for content that uses the assets in the merge file.