Web Server Connection State Sharing to Eliminate Load Balancer Hops
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for connecting web servers and web application servers require additional network hops and equipment, leading to performance degradation and inefficiencies, especially in dynamic cloud environments.
Innovation Solution
A method where a WAS admin server manages and shares connection state information between existing and new web servers and web application servers, eliminating the need for an additional network hop by directly managing TCP connections and state changes within the existing infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If an ELB is installed between web servers and WAS to support dynamic configuration, then adaptability is improved, but device complexity increases and network hop increases
Solution Approach 1:
The patent extracts the load balancing and dynamic configuration management functions from the ELB device and integrates them directly into the web server and WAS software. This eliminates the need for the separate ELB hardware while preserving the dynamic configuration capability through software-based connection state information sharing.
Solution Approach 2:
The patent merges the functions of the ELB into the existing web server and WAS infrastructure. By combining the load balancing, connection management, and dynamic configuration capabilities into the software layers already present in the system, the patent eliminates the need for separate ELB equipment while maintaining adaptability.
2Adaptability or versatility
If an ELB is used for dynamic configuration, then adaptability is improved, but network hop increases leading to performance degradation
Solution Approach 1:
The patent removes the intermediate ELB hop from the request path by extracting its functions and implementing them directly in the web server and WAS. This creates a direct connection path between web servers and WAS, eliminating the additional network hop while maintaining dynamic configuration through software-based information sharing.
3Adaptability or versatility
If ELB is used to manage dynamic configuration, then adaptability is improved, but productivity decreases due to performance degradation
Solution Approach 1:
The patent extracts the ELB's management functions and implements them natively in the web server and WAS software. This eliminates the performance bottleneck created by the intermediate ELB device while preserving dynamic configuration capabilities, thereby improving system throughput and productivity.
Solution Approach 2:
The patent introduces connection state information as a software-based intermediary mechanism that enables dynamic configuration without requiring physical ELB equipment. This information-mediated approach allows the system to achieve adaptability while maintaining direct communication paths, thus preserving productivity.
4Adaptability or versatility
If ELB is deployed for dynamic configuration, then adaptability is improved, but device complexity increases due to additional equipment
Solution Approach 1:
The patent merges the ELB's load balancing and dynamic configuration management functions into the existing web server and WAS software components. This consolidation eliminates the need for separate ELB equipment and reduces infrastructure complexity while maintaining full adaptability through software-based connection state information sharing.
Solution Approach 2:
The patent makes the existing web server and WAS software multi-functional by enabling them to perform both their original functions and the ELB's load balancing and dynamic configuration management functions. This universal approach eliminates the need for specialized ELB equipment while preserving adaptability.
Data Source
AI summary
A method for connecting webservers and web application servers (WAS's) is provided. The method includes steps of: (a) a WAS admin server, while managing multiple existing WAS managed servers and communicating with multiple existing webservers, if a new webserver except the multiple existing webservers or a new WAS managed server except the multiple existing WAS managed servers is determined as being operated, receiving connection state information of the new webserver or that of the new WAS managed server; and (b) the WAS admin server delivering the connection state information of the new webserver or that of the new WAS to the multiple existing WAS managed servers and the multiple existing webservers.


