Non-DSR Load Balancer with Virtualized VIPS and Source Proxy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current load balancing techniques face inefficiencies as they process data packets at higher layers of the network stack, leading to increased processing times and a need for improved methods to distribute data loads across multiple nodes in a virtual network.
Innovation Solution
Implementing a management component associated with a virtual switch that performs load balancing at the data link layer by translating source and destination IP addresses to virtual addresses, allowing data packets to be routed efficiently across container hosts, thereby reducing CPU cycles and enhancing throughput.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If load balancing is performed at higher layers of the network stack, then routing decisions can be made with more information, but processing times increase
Solution Approach 1:
The patent extracts the load balancing decision-making process from the traditional higher-layer processing (Layer 4/7) and relocates it to Layer 2 (data link layer) through the use of source proxy virtual IP addresses. This extraction allows routing decisions to be made at a lower layer where processing is faster, while still maintaining the ability to make informed routing decisions through the source proxy mechanism that tracks connection states
Solution Approach 2:
The source proxy virtual IP address acts as an intermediary between the client and the actual server nodes. It mediates the load balancing process by receiving packets at Layer 2, making routing decisions based on connection state information, and forwarding packets to appropriate servers. This intermediary approach enables faster Layer 2 processing while maintaining the intelligence of higher-layer load balancing
2Measurement precision
If load balancing is performed at higher layers of the network stack, then more accurate routing decisions can be made, but CPU cycles increase
Solution Approach 1:
The patent extracts the computationally intensive load balancing operations from higher-layer processing where they consume significant CPU cycles, and relocates them to Layer 2 processing. By implementing the source proxy mechanism at the data link layer, the system makes routing decisions with less CPU overhead while maintaining routing accuracy through connection state tracking
Solution Approach 2:
The patent substitutes traditional software-based load balancing mechanisms (which require extensive CPU processing at Layers 4/7) with a hardware-accelerated Layer 2 switching approach. The source proxy virtual IP addresses enable the use of faster Layer 2 switching fabric and hardware-based routing decisions, reducing the mechanical processing burden on CPUs
3Measurement precision
If traditional load balancing methods are used, then routing decisions can be made with full packet information, but scalability is limited
Solution Approach 1:
The patent introduces a new dimension to load balancing by adding source proxy virtual IP addresses at Layer 2, creating a multi-dimensional addressing scheme. This allows the system to scale by adding more virtual IP addresses and server nodes without fundamentally changing the core load balancing mechanism. The Layer 2 switching fabric provides a scalable backbone that can handle increasing numbers of connections and nodes
Data Source
AI summary
Methods and devices for load balancing of connections may include receiving, at a management component on a container host on a computer device, at least one data packet based on a destination IP address of the data packet that corresponds to a plurality of container hosts. The methods and devices may include selecting a destination container from at least one container host on the computer device and other computer devices in communication with the computer device over a virtual network to balance a data load and translating the source IP address of the at least one data packet to a local IP address of the container host. The methods and devices may include changing the destination IP address of the at least one data packet to a virtual IP address of the selected destination container so that the at least one data packet is transformed to a proxy data packet.