Inverted Load Balancer Connection Pool for Distributed Data Centers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

As data centers become more distributed and dynamic, providing effective load balancing across multiple data centers is challenging due to the increased complexity of managing a larger number of servers and varying network configurations, including those separated by firewalls and public networks.

Innovation Solution

A system and method that utilize a load balancer executing on a device intermediary to servers and clients, employing an inverted connection pool where load balancing agents proactively establish connections with the load balancer, allowing for dynamic management of transport layer connections based on server availability and client requests, and maintaining a predetermined number of connections through policies and authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data centers become more distributed and dynamic with a larger number of servers, then server availability and flexibility improve, but load balancing complexity and difficulty of managing connections increase

Engineering Contradiction:

Improveserver availabilityVSAvoidload balancing complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Instead of having the load balancer proactively establish connections to servers (traditional approach), the patent inverts the approach by having servers or agents on servers proactively establish connections to the load balancer. This inversion simplifies the load balancer's role and reduces its complexity while maintaining adaptability to distributed data center environments.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

Servers or agents on servers autonomously manage their own connections to the load balancer by proactively establishing and maintaining connections. This self-service approach reduces the management overhead on the load balancer and simplifies the overall system complexity while preserving server availability and flexibility.

Inventive Principle:

Principle #25Self-service

2Adaptability or versatility

If servers are separated by firewalls and public networks in distributed data centers, then data center distribution and flexibility improve, but connection management and network performance deteriorate

Engineering Contradiction:

Improvedata center distributionVSAvoidnetwork performance

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

Servers or agents proactively establish connections to the load balancer in advance, before client requests arrive. This preliminary action ensures that connections are already available and optimized when needed, improving network performance across distributed data centers separated by firewalls and public networks.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The load balancer acts as an intermediary that receives proactive connections from servers and then manages client requests. This intermediary role facilitates efficient connection management across distributed networks, maintaining performance despite the presence of firewalls and public network infrastructure.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If the load balancer proactively establishes connections to servers, then connection control improves, but the number of connections and system resource consumption increase

Engineering Contradiction:

Improveconnection controlVSAvoidnumber of connections

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

The patent inverts the connection initiation approach so that servers or agents establish connections to the load balancer rather than the load balancer establishing connections to servers. This inversion maintains connection control while potentially reducing the total number of connections the load balancer must actively manage.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

Servers or agents autonomously manage their own connections to the load balancer, which reduces the connection management burden on the load balancer and can reduce the overall number of connections in the system while maintaining operational control.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS11553037B2Systems and methods for providing load balancing as a service

Publication Date: 2023.01.10 CITRIX SYSTEMS INC

AI summary

The present disclosure is directed generally to systems and methods for providing load balancing as a service. A load balancer executing on a device intermediary to a server and a plurality of clients can receive a request from an agent executing on the server. The request can be to initiate establishment of a transport layer connection. The load balancer can accept the request to establish the transport layer connection with the server. The load balancer can receive a request to access the server from a client of the plurality of clients. The load balancer can forward the request to the server via the transport layer connection established between the load balancer and the server responsive to the request of the server.