Web Scripting Session Tracking for Load Balancing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Server-side web scripting can lead to slower user experiences and increased server load due to the need for additional network requests, and traditional load balancing techniques may fail to route user input to the correct server, disrupting ongoing web sessions.
Innovation Solution
A system with an intermediary web scripting tracking component and a common data store is implemented, allowing for efficient management of web browsing sessions across multiple enterprise servers, enabling seamless reconnection and scaling of web sessions by tracking session identifiers and request information, and facilitating communication between client devices and third-party websites.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If server-side web scripting is used to provide customized interfaces, then user interface customization is improved, but network request frequency increases and user experience speed deteriorates
Solution Approach 1:
The system performs preliminary actions by pre-fetching and caching data that will be needed for future web script executions. The intermediary component stores data in advance based on predicted user needs and script requirements, so that when scripts need to execute, the data is already available locally or in a readily accessible cache, eliminating the need for additional network requests during script execution.
Solution Approach 2:
An intermediary component is introduced between the web server and the data storage system. This intermediary pre-loads and caches data before it is actually needed by web scripts, acting as a buffer that anticipates data requirements. The intermediary uses prediction algorithms to determine what data will be needed and retrieves it in advance, thereby reducing network traffic during actual script execution and improving user experience speed while maintaining customization capabilities.
2Productivity
If traditional load balancing techniques are used to distribute requests, then server load distribution is improved, but web session continuity deteriorates due to incorrect routing of user input
Solution Approach 1:
The system implements a feedback mechanism where the load balancing component continuously monitors which server is currently handling each web session and uses this information to make routing decisions. When user input arrives, the system checks the feedback data to determine which server should receive the input to maintain session continuity. This feedback loop ensures that load balancing decisions are made with knowledge of active sessions, preventing the routing of user input to incorrect servers while still distributing load effectively across the server farm.
3Productivity
If multiple enterprise servers are used to scale web browsing sessions, then system capacity and scalability are improved, but session tracking complexity and data management burden increase
Solution Approach 1:
The system merges the session tracking functionality into a unified data structure that is shared across all enterprise servers. Instead of each server maintaining separate session state information, the system combines all session tracking data into a common format stored in accessible memory or cache. This merging approach allows any server to handle any session without complex routing logic, as the unified data structure provides a consistent view of all sessions across the distributed system, reducing tracking complexity while maintaining high system capacity.
Data Source
AI summary
Disclosed are techniques and apparatuses that are configured to receive an indication that a web browsing session executing on an enterprise server needs additional information based on a request for additional information being sent to a client device. The request may include an identifier of the web browsing session and an identifier of an enterprise server that initiated the web browsing session. A globally unique identifier related to the web browsing session and an identifier of the enterprise server is stored in a common data store. The web browsing session may be paused when the web browsing session requests additional information from a client device. The client device may respond with the additional information. The system may provide the identifier of the enterprise server to a load balancing component so the identified web browsing session executing on the enterprise server may continue to be used.