Client-Side Website Rendering via Distributed CDN Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional server-based website hosting architectures face issues such as slow service during high demand, service interruptions, and susceptibility to DDoS attacks, relying on costly hosting services for computing power.
Innovation Solution
A distributed content delivery network (CDN) and a rendering engine application are used on client devices to merge website-specific and generic template data, allowing website rendering without dependence on a single server, incorporating cloud-based storage and third-party plug-ins for enhanced functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If website content and code are stored on a single centralized server, then the server can manage and deliver website content, but the service becomes slow during high demand and susceptible to DDoS attacks
Solution Approach 1:
The patent segments the centralized website hosting function into distributed components across multiple client devices. Each client device stores and renders website content locally using a rendering engine application, eliminating the single point of failure. The website is divided into template configuration files stored in cloud-based storage and rendered locally on client devices, distributing the service across many nodes instead of one centralized server.
Solution Approach 2:
The patent introduces a rendering engine application as an intermediary layer between the cloud-based storage and the website content delivery. This intermediary enables client devices to locally process and render website content without requiring continuous connection to or dependency on a centralized hosting server, thereby protecting against DDoS attacks while maintaining service availability.
2Ease of manufacture
If website content is hosted on a remote server, then centralized management is achieved, but service interruption occurs when the hosting server is down
Solution Approach 1:
The patent segments the website hosting architecture into distributed client-side rendering components. Each client device independently stores and renders website content using template configuration files from cloud-based storage, eliminating the single point of failure. This segmentation allows centralized updates through cloud storage while maintaining local service continuity even when remote servers are down.
Solution Approach 2:
The patent implements preliminary action by pre-storing template configuration files in cloud-based storage that can be accessed by multiple client devices. This allows website content to be prepared and cached in advance, enabling client devices to render websites locally without real-time dependency on the remote hosting server, ensuring service continuity during server downtime.
3Reliability
If costly website hosting services are used, then professional website management is provided, but cost-effectiveness is reduced
Solution Approach 1:
The patent enables self-service by empowering client devices to independently store, process, and render website content using template configuration files from cloud-based storage. This eliminates the need for costly professional hosting services while maintaining reliable website delivery. The rendering engine application on each client device performs the work previously done by expensive hosting infrastructure, making the system cost-effective while preserving professional-quality website presentation.
Solution Approach 2:
The patent uses copying by distributing template configuration files from cloud-based storage to multiple client devices. Each client device maintains a local copy of the website content and rendering engine, eliminating the need to pay for expensive centralized hosting services. This copying approach allows professional-quality website rendering at each client location without incurring high hosting costs.
Data Source
AI summary
Disclosed herein is a novel system and method for website rendering. In exemplary embodiments, the system and method comprise downloading a rendering engine onto a client device. The rendering engine retrieves or downloads website-specific data and website template data. The rendering engine merges the website-specific data and website template data. The rending engine obtains website assets identified by the merged data, and a template .css file. The rendering engine renders a website utilizing the merged data, the assets and the .css file.