Self-managed Overlay Network for Cross-Datacenter Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for inter-datacenter networking are inefficient, requiring significant management resources and complex routing logic, especially when scaling distributed applications across multiple datacenters, leading to higher latency and packet loss.

Innovation Solution

A self-managing overlay network is created by a cluster manager that provides cluster membership, topology, and routing, allowing distributed applications to replicate data and segregate functionality based on instance location without directly managing the cluster topology, enabling direct cross-datacenter communication and minimizing traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If datacenter-aware processing is built into the distributed application to track instance locations and route data, then communication efficiency between datacenters is improved, but development resources and device complexity increase significantly

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidrouting logic complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a cluster manager as an intermediary component that handles all routing and topology management. The cluster manager maintains the cluster topology and provides routing services to application instances, allowing applications to communicate efficiently across datacenters without embedding complex routing logic within them. This mediator approach resolves the contradiction by externalizing the complexity while maintaining communication efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the routing functionality from the application instances and places it in the cluster manager. This segmentation allows the application instances to remain simple while the cluster manager handles the complex routing and topology management, thus improving communication efficiency without increasing application complexity.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If a centralized federated management system is used to control application instances across datacenters, then routing management is simplified, but management resources and setup requirements increase

Engineering Contradiction:
Improverouting management easeVSAvoidmanagement infrastructure complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The cluster manager implements self-service mechanisms by automatically discovering application instances, maintaining the cluster topology, and dynamically providing routing information. The system self-configures as instances join and leave the cluster, eliminating the need for manual setup and reducing management infrastructure complexity while maintaining ease of operation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The cluster manager continuously monitors the cluster topology and provides real-time feedback to application instances about their peers and routing paths. This feedback mechanism enables dynamic routing adjustments without manual intervention, simplifying management while reducing the need for complex pre-configured infrastructure.

Inventive Principle:
Principle #23Feedback

3Device complexity

If all application instances form a fully connected graph to simplify routing, then routing logic is reduced, but deployment flexibility is compromised due to policy or security concerns

Engineering Contradiction:
Improverouting logic complexityVSAvoiddeployment flexibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The cluster manager acts as a mediator that enables full mesh communication semantics without requiring actual full mesh connectivity. It translates communication requests between instances, allowing applications to interact as if fully connected while actually routing through the cluster manager, thus maintaining deployment flexibility and security policies.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The cluster manager provides universal routing capabilities that work regardless of the underlying network topology or security constraints. It handles various deployment scenarios (fully connected, partially connected, hierarchical) through a single unified mechanism, maintaining adaptability while keeping routing logic simple for applications.

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

4Speed

If cross-datacenter traffic is routed directly between instances, then communication speed is improved, but latency and packet loss increase

Engineering Contradiction:
Improvecommunication speedVSAvoidcommunication reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The cluster manager serves as a mediator that optimizes cross-datacenter traffic routing. It maintains knowledge of instance locations and network conditions, allowing it to route traffic through optimal paths that balance speed and reliability, rather than direct instance-to-instance routing which suffers from latency and packet loss.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The cluster manager performs preliminary routing decisions based on maintained topology information before traffic is sent. It pre-determines optimal paths considering network conditions and instance locations, improving both speed and reliability by avoiding ad-hoc direct routing that encounters network issues.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10122626B2Self-managed overlay networks
Publication Date: 2018.11.06 VMWARE INC
  • US10122626B2 patent drawing
  • US10122626B2 patent drawing
  • US10122626B2 patent drawing

AI summary

Some embodiments provide a method for processing data messages through an overlay network for a cluster of application instances operating on machines located across several datacenters. The method receives a data message, from a first application instance of the cluster operating on a first machine in a first datacenter, destined to a second application instance. When the second application instance operates on a machine in a different, second datacenter, the method (i) encapsulates the data message according to an overlay network defined for the cluster and (ii) forwards the encapsulated data message to a publicly accessible machine of the second datacenter. Only a subset of the application instances operating in the second datacenter operate on publicly accessible machines. When the second application instance operates on a machine in the first datacenter, the method forwards the data message directly to the machine on which the second application instance operates.