CDN Proxy Servers Automate Static Content Upload
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing content delivery network (CDN) systems face inefficiencies in manually uploading and migrating large volumes of content, particularly during peak usage or when dealing with origin site problems such as traffic overload or DoS attacks, as manual upload processes are cumbersome and inadequate.
Innovation Solution
Implementing an automated and on-demand upload capability within the CDN platform using proxy servers that generate upload commands for network storage, allowing for safe ingestion of content from a content provider origin infrastructure, distinguishing between static and dynamic objects, and enabling asynchronous object retrieval and storage in network storage subsystems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual upload processes are used for content migration, then content can be uploaded to CDN network storage, but the process is cumbersome and inadequate during peak usage or origin site problems
Solution Approach 1:
The system pre-configures upload commands and instructions in the CDN platform before content needs to be migrated. When content requests are received, the pre-prepared infrastructure enables immediate automated upload without manual intervention, resolving the contradiction between ease of operation and migration efficiency.
Solution Approach 2:
The CDN platform automatically generates upload commands and retrieves content from origin infrastructure without human intervention. The system serves itself by autonomously migrating content based on detected requests, eliminating the cumbersome manual upload process while maintaining high productivity.
2Productivity
If automated upload commands are generated by proxy servers, then content migration efficiency is improved, but system complexity increases
Solution Approach 1:
The CDN platform is designed with multi-functional proxy servers that can both serve content requests and generate upload commands. This universal infrastructure handles multiple tasks within existing components, improving migration efficiency without proportionally increasing system complexity.
Solution Approach 2:
Proxy servers act as intermediaries between clients and network storage, automatically generating upload commands when content is requested. This intermediary layer simplifies the overall architecture by centralizing the automation logic in a single component type rather than requiring complex coordination between multiple specialized systems.
3Reliability
If all content objects are uploaded to network storage, then content delivery is improved, but dynamic and personalized content should not be uploaded
Solution Approach 1:
The system applies different upload behaviors to different content objects based on their characteristics. Static content objects are automatically uploaded to network storage for reliable delivery, while dynamic and personalized content objects are identified and excluded from upload. This localized quality approach resolves the contradiction by treating different content types differently within the same system.
Solution Approach 2:
Instead of uploading all content and then filtering, the system inverts the approach by identifying content that should NOT be uploaded (dynamic and personalized content) and excluding it from the upload process. This inversion ensures that only appropriate static content is migrated, maintaining both delivery reliability and content type adaptability.
Data Source
AI summary
According to certain non-limiting embodiments disclosed herein, the functionality of a distributed computing platform, such as a content delivery network with network storage, is improved by providing automated and on-demand upload capability into the network storage. In one embodiment, the platform is made up of many proxy servers. As clients request content from the proxies, they generate upload commands for the network storage subsystem to ingest the content from a content provider origin infrastructure. Preferably, the proxy servers are configured to generate ‘safe’ upload commands such that objects are not ingested if they contain sensitive information and/or are personalized and/or might be dynamically generated objects. Thus, relatively safe ‘static’ objects can be automatically uploaded and migrated from a content provider origin, as client requests arrive.


