Load Balancing via Load Projections for Event Traffic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Social networking services face challenges in managing load balancing during high-demand events, such as live events, where data centers become congested, leading to delayed responses due to the inability of traditional load balancers to handle rapid increases in load effectively.

Innovation Solution

A computing system that predicts and projects future loads using a load characterization mechanism, redirecting traffic to a secondary content delivery network (CDN) when projected loads exceed capacity thresholds, thereby preventing overloading at access points.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional load balancers are used to distribute traffic to data centers, then basic load balancing is achieved, but the system cannot handle rapid increases in load during high-demand events, causing data centers to become congested and responses to be delayed

Engineering Contradiction:
Improveload handling capabilityVSAvoidresponse delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by predicting future load conditions before they occur. The load prediction module analyzes current traffic patterns and event data to forecast upcoming demand spikes, allowing the load balancer to proactively redirect traffic to appropriate data centers before congestion occurs, thereby preventing response delays

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring actual load conditions at data centers and comparing them against predicted values. This real-time feedback allows the load balancing system to dynamically adjust traffic distribution decisions, improving productivity while maintaining timely responses by correcting deviations from optimal load distribution

Inventive Principle:
Principle #23Feedback

2Reliability

If traffic is redirected to a different data center that is farther away to balance load, then congestion at the original data center is reduced, but network latency increases due to the greater distance

Engineering Contradiction:
Improveload balance effectivenessVSAvoidnetwork response speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system applies local quality by making load balancing decisions specific to each data center's capacity, location, and current load conditions. Instead of uniform load distribution, the system evaluates individual data center characteristics and routes traffic to the most appropriate location, maintaining both load balance effectiveness and network response speed by selecting optimal destinations based on local conditions

Inventive Principle:
Principle #3Local quality

3Productivity

If the system monitors and predicts load in real-time to prevent overloading, then optimal load distribution is achieved, but system complexity increases due to the need for prediction algorithms and real-time monitoring

Engineering Contradiction:
Improveload distribution efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system achieves universality by designing a load prediction module that can handle multiple types of events and traffic patterns using a single unified algorithmic framework. This multi-functional approach improves load distribution efficiency across diverse scenarios while avoiding the complexity of maintaining separate specialized systems for each event type

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10348630B2Load balancing based on load projections for events
Publication Date: 2019.07.09 META PLATFORMS INC
  • US10348630B2 patent drawing
  • US10348630B2 patent drawing
  • US10348630B2 patent drawing

AI summary

A computing system operates according to a method including: identifying communication of data; determining a current load measure for characterizing an egress measure associated with the data at a current time; generating a load projection for characterizing the egress measure at the access point corresponding to a future time; and generating an assigned address based on the load projection.