Client-Side Rendering Engine for Distributed Website Hosting
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 malicious attacks like DDoS, due to reliance on a single centralized server.
Innovation Solution
A distributed content delivery network (CDN) and a rendering engine downloaded to client devices merge website and template configuration files to render websites, utilizing cloud-based storage and client device computing power, thereby reducing dependence on single servers and enhancing resilience against attacks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If website content and code are stored on a single centralized server, then website management and rendering are simplified, but service speed deteriorates under high demand and reliability deteriorates due to single point of failure
Solution Approach 1:
The patent segments the centralized website hosting architecture into a distributed network of edge servers and client devices. Website content is divided and cached across multiple edge servers geographically distributed around the world, while rendering functionality is segmented and executed locally on client devices through downloaded rendering engines. This segmentation eliminates the single point of failure by distributing content across multiple nodes and performing rendering at the edge, thereby improving service availability and reliability.
Solution Approach 2:
The patent introduces a new dimension to website hosting by moving from a single centralized server model to a multi-dimensional distributed architecture. Content is replicated across multiple spatial dimensions (different edge servers in different locations), and rendering is distributed across temporal dimensions (on-demand download and execution on client devices). This dimensional expansion transforms the architecture from vulnerable centralized to resilient distributed, improving reliability without sacrificing management simplicity.
2Loss of energy
If website content is hosted on a single server, then hosting cost is reduced, but service speed deteriorates during high demand periods
Solution Approach 1:
The patent applies preliminary action by pre-caching website content on multiple edge servers before user requests arrive. Content is proactively replicated and stored across the distributed edge network in advance, so when high demand occurs, users can access content from the nearest edge server with minimal latency. This preliminary distribution of content eliminates the need for costly centralized server scaling while maintaining high service speed during demand peaks.
Solution Approach 2:
The patent uses copying by replicating website content across multiple edge servers instead of relying on a single original server. Each edge server maintains a copy of the content, allowing any of them to serve requests independently. This copying strategy distributes the load across multiple low-cost edge servers, maintaining fast service speed during high demand without requiring expensive centralized hosting infrastructure.
3Ease of manufacture
If centralized server hosting is used, then implementation is simplified, but susceptibility to malicious attacks increases
Solution Approach 1:
The patent introduces edge servers as intermediaries between the centralized content source and end-user client devices. These intermediary edge servers cache and serve content locally, creating a buffer that protects the original content source from direct exposure to malicious attacks. Even if edge servers are compromised, the distributed architecture prevents single-point attacks from affecting the entire system, thereby reducing attack susceptibility while maintaining implementation simplicity through automated content propagation.
Solution Approach 2:
The patent enables self-service by allowing edge servers and client devices to autonomously download, cache, and execute rendering operations without requiring continuous centralized server involvement. This self-sufficient distributed architecture reduces the attack surface by minimizing dependencies on centralized servers, as each node can operate independently. The system maintains simplicity through automated self-configuration and content propagation while inherently resisting attacks through decentralized autonomy.
4Loss of energy
If rendering is performed on client devices, then hosting cost is reduced by utilizing client computing power, but device complexity increases
Solution Approach 1:
The patent applies universality by designing a standardized rendering engine that can execute on diverse client devices with varying capabilities. The rendering engine is built to adapt to different device types (mobile, desktop, tablet) and operating systems, providing universal rendering functionality across the ecosystem. This multi-functional approach allows client devices to perform rendering tasks independently, reducing hosting costs while maintaining consistent implementation across different device complexities through a unified rendering framework.
Data Source
AI summary
Disclosed herein is 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 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.