Cross-Datacenter Task Routing for Cloud Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing distributed/cloud processing systems fail to effectively manage task distribution across multiple data centers, leading to unbalanced load and inefficiencies in task processing due to lack of knowledge about the load conditions in other data centers.

Innovation Solution

A method and system that utilize a cross-datacenter storing device to facilitate task distribution between data centers by receiving tasks from one data center and transmitting them to another if local servers are unavailable, ensuring optimal resource utilization across multiple data centers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If tasks are processed only within a single data center, then task processing is simple to manage, but load balancing across multiple data centers cannot be achieved

Engineering Contradiction:
Improvetask management simplicityVSAvoidtask processing efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

A task management server is introduced as an intermediary component that coordinates task distribution between multiple data centers. This server receives tasks from clients, determines appropriate data centers based on load conditions, and routes tasks accordingly, thereby achieving load balancing without requiring complex direct coordination between data centers

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments task management functions into separate components: task reception, load condition monitoring, and task routing. Each data center operates independently with its own task execution resources, while the task management server provides centralized coordination, allowing scalable expansion across multiple data centers

Inventive Principle:
Principle #1Segmentation

2Productivity

If tasks are distributed across multiple data centers, then load balancing improves, but system complexity increases due to lack of knowledge about load conditions in other data centers

Engineering Contradiction:
Improvetask processing efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Each data center continuously monitors its own load conditions and provides feedback to the task management server. The server uses this feedback information to make informed routing decisions, dynamically adjusting task distribution based on real-time or near-real-time load status of each data center

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The task management server acts as a central intermediary that consolidates load information from multiple data centers, simplifying the complexity by providing a single point of decision-making rather than requiring direct peer-to-peer communication between all data centers

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If tasks are queued locally when servers are unavailable, then task loss is prevented, but task processing time increases

Engineering Contradiction:
Improvetask completion guaranteeVSAvoidtask waiting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary checks of data center load conditions before routing tasks. When a data center is determined to be overloaded or unavailable, the task management server proactively routes the task to an alternative data center in advance, preventing task queuing delays by anticipating availability issues

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10324764B2Method and system for processing tasks in a cloud service
Publication Date: 2019.06.18 Y E HUB ARMENIA LLC
  • US10324764B2 patent drawing
  • US10324764B2 patent drawing
  • US10324764B2 patent drawing

AI summary

There are provided a method and a system for processing tasks in a cloud service. The method comprises: receiving, by the first controlling electronic device, a first task; determining whether at least one server within a plurality of servers of the first data center being available for performing the first task; responsive to the at least one server within the plurality of servers of the first data center being available for performing the first task, assigning the first task to said at least one available server; responsive to none server within the plurality of servers of the first data center being available for performing the first task, transmitting said first task to at least one cross-datacenter storing device, the at least one cross-datacenter storing device is configured to transmit the first task to the second controlling electronic device responsive to receiving a request from the second controlling electronic device.