Anycast DNS Load Balancing via Dynamic Address Advertising

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing distributed content server systems using anycast addresses are not load-aware, leading to potential overloading of content servers, as requests are routed based on proximity rather than server load, resulting in inefficient load balancing across geographically distributed servers.

Innovation Solution

Implementing a method within the DNS system that includes an anycast module and a load balancing module to select and manage anycast network addresses, where load information from content servers is used to instruct overloaded servers to cease advertising certain anycast addresses, thereby redistributing the load across available servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If anycast addresses are used for routing requests to content servers, then request routing efficiency is improved, but server load balancing deteriorates

Engineering Contradiction:
Improverequest routing efficiencyVSAvoidserver load balancing
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The system dynamically adjusts the advertising status of anycast addresses based on real-time server load conditions. When a server becomes overloaded, the DNS server stops advertising its anycast address, automatically redirecting new requests to other servers. This dynamic adjustment resolves the contradiction by making the routing system adaptable to changing load conditions while maintaining routing efficiency.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements a feedback mechanism where the DNS server receives load information from content servers and adjusts anycast address advertising accordingly. This closed-loop control ensures that routing decisions are based on current server capacity, preventing overload while maintaining efficient request distribution across the network.

Inventive Principle:
Principle #23Feedback

2Loss of time

If requests are routed based on proximity to anycast addresses, then network latency is reduced, but server overload increases

Engineering Contradiction:
Improvenetwork latencyVSAvoidserver overload
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system transitions from a static proximity-based routing approach to a dynamic load-aware routing approach. The DNS server continuously monitors server load and adjusts anycast address advertising in real-time, ensuring that requests are routed to geographically proximate servers only when they have capacity, thus reducing latency while preventing overload.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Load information feedback from content servers to the DNS server enables the system to adjust routing behavior based on current server capacity. This feedback mechanism ensures that proximity-based routing does not lead to server overload, as overloaded servers automatically stop advertising their anycast addresses, redirecting requests to other capable servers.

Inventive Principle:
Principle #23Feedback

3Reliability

If multiple anycast addresses are advertised by all content servers, then service availability is improved, but load distribution efficiency deteriorates

Engineering Contradiction:
Improveservice availabilityVSAvoidload distribution efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system segments the anycast address advertising function by server, allowing each server to independently control its anycast address advertising based on its load conditions. This segmentation enables fine-grained load distribution while maintaining service availability, as individual servers can be taken offline from anycast routing without affecting the entire system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically controls which servers advertise anycast addresses based on real-time load conditions. Servers with available capacity advertise their anycast addresses to receive requests, while overloaded servers stop advertising to redirect traffic. This dynamic approach optimizes load distribution efficiency while ensuring service availability through multiple advertising servers.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3591944B1An anycast based, wide area distributed mapping and load balancing system
Publication Date: 2021.03.10 GOOGLE LLC
  • EP3591944B1 patent drawingFigure 1
  • EP3591944B1 patent drawingFigure 2
  • EP3591944B1 patent drawingFigure 3

AI summary

This disclosure provides systems, methods, and apparatus for providing anycast based load balancing for a plurality of servers within a network. The network includes a domain name system (DNS) server that is configured to respond to domain name queries received from one or more clients. The DNS server maintains a set of anycast IP addresses associated with a domain name. The DNS server responds to a client's request with one or more selected anycast IP addresses from the set of anycast IP addresses. The DNS server also instructs a plurality of content servers to advertise all of the anycast IP addresses to the network. The DNS server also receives load information from each of the plurality of content servers, and instructs, based on the load information, one of the plurality of content servers to cease advertising one or more of the previously advertised anycast IP addresses.