On-Demand Web-Server Instances for Isolated Custom Backends
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional website development systems lack the capability to create dynamic webpages with customizable backend functionality, require significant user involvement in server management, suffer from processing delays, and are vulnerable to malicious plugins affecting multiple websites.
Innovation Solution
A system that allows users to add backend functionality to centrally hosted websites with a unified interface, enabling dynamic webpage editing and preview, and provides on-demand webserver instances for instant response, while isolating plugins to prevent cross-infection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users add custom backend functionality to websites, then website functionality and customization are improved, but system complexity and security vulnerability increase
Solution Approach 1:
The system segments backend functionality into isolated execution environments (containers or virtual machines) for each website. Each website's custom backend code runs in its own isolated environment, preventing conflicts and security vulnerabilities from spreading between sites while maintaining full customization capability.
Solution Approach 2:
The system introduces a managed backend execution environment as an intermediary layer between the website frontend and the server infrastructure. This intermediary handles all backend processing, database interactions, and API calls, allowing users to add functionality without directly managing system complexity.
2Adaptability or versatility
If users manage server interactions directly, then control and customization are improved, but ease of operation deteriorates
Solution Approach 1:
The system provides self-service capabilities where users can add backend functionality through simple code snippets or visual builders without needing to understand server management. The platform automatically handles deployment, scaling, and infrastructure management, allowing users to focus only on their specific functionality needs.
3Quantity of substance
If websites use shared server resources, then cost efficiency is improved, but response time and processing speed deteriorate
Solution Approach 1:
The system dynamically allocates server resources based on actual website traffic and processing needs. When a website requires additional computational resources, the system automatically spins up dedicated execution instances; when traffic decreases, resources are released or pooled for other websites, optimizing both response time and resource utilization.
4Adaptability or versatility
If plugins are installed on shared servers, then functionality is improved, but security reliability deteriorates due to cross-infection
Solution Approach 1:
The system implements strict segmentation by running each website's plugins and backend code in isolated containers or virtual machines. This ensures that malicious plugins or security vulnerabilities in one website cannot affect other websites sharing the same physical or virtual infrastructure, while still allowing rich plugin functionality to be installed.
Data Source
AI summary
An online website building system includes: an online database configured to store a library of website building elements for configuring a front-end of a webpage, the webpage having been built on a platform including at least common server code; and store rules for accessing code associated with the website building elements; and at least one processor configured to enable the user to edit code associated with a webpage, and to provide a programmable event for activating the resultant user-editable code, where the user-editable code is configured to provide dynamic customized back-end functionality associated with the webpage; store the edited user-editable code in a code storage system in communication with the online database; receive a request to access the webpage, and in response to the request and before the request times out, provide access to a virtualized execution instance comprising at least the common server code and the edited user-editable code.


