Distributed Computing Failover via Predefined Orchestrations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern computing systems face challenges in maintaining optimal performance and efficiently managing large amounts of data and transactions across multiple servers and datacenters, particularly in scenarios where failures occur, leading to suboptimal system resilience and resource allocation inefficiencies.
Innovation Solution
A failure-resistant distributed computing system is implemented, comprising primary and secondary datacenters with interconnected messaging queues and a control center that orchestrates failover operations by shifting tasks from one datacenter to another, ensuring high availability and efficient resource allocation through predefined orchestrations executed by computerized servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a distributed computing system with multiple datacenters is implemented, then system reliability and availability are improved, but device complexity and resource allocation management become more difficult
Solution Approach 1:
The patent introduces a control center as an intermediary component that manages orchestrations between primary and secondary datacenters. The control center receives failure notifications, selects appropriate failover orchestrations from a predefined list, and transmits execution commands to processing nodes, thereby simplifying the complexity of direct peer-to-peer coordination between datacenters.
Solution Approach 2:
The system pre-configures multiple orchestrations in a predefined list before failures occur. These orchestrations include failover operations that have already been planned and validated. When a failure is detected, the control center simply selects from these pre-prepared orchestrations rather than creating failover plans in real-time, reducing decision complexity during critical failure events.
2Reliability
If failover operations are implemented to shift tasks between datacenters, then system resilience is improved, but task execution time and resource allocation efficiency may deteriorate
Solution Approach 1:
The system prepares multiple failover orchestrations in advance, with each orchestration containing pre-determined task migration paths and resource allocation strategies. When a failure occurs, the control center can immediately activate a pre-planned orchestration without needing to compute failover routes in real-time, significantly reducing the time loss during failover operations.
Solution Approach 2:
The patent maintains copies of orchestrations in the control center's memory and transmits them to processing nodes as needed. The system creates and stores multiple copies of failover procedures, allowing rapid deployment of proven failover strategies without re-computation, thereby minimizing task execution time delays during failure events.
3Speed
If multiple orchestrations are pre-configured for failover operations, then failover speed is improved, but memory requirements and system resource consumption increase
Solution Approach 1:
The control center is designed with universal memory structures that store orchestrations in a standardized format. The same memory infrastructure supports multiple orchestrations with varying complexity, allowing the system to maintain several failover plans without proportionally increasing resource consumption. The universal design enables efficient memory utilization across different orchestration scenarios.
Data Source
AI summary
A failure resistant distributed computing system includes primary and secondary datacenters each comprising a plurality of computerized servers. A control center selects orchestrations from a predefined list and transmits the orchestrations to the datacenters. Transmitted orchestrations include less than all machine-readable actions necessary to execute the orchestrations. The datacenters execute each received orchestration by referencing a full set of actions corresponding to the received orchestration as previously stored or programmed into the computerized server and executing the referenced full set of actions. At least one of the orchestrations comprises a failover operation from the primary datacenter to the secondary datacenter. Failover shifts performance of task from a set of processing nodes of the primary datacenter to a set of processing nodes of the secondary datacenter, such tasks including managing storage accessible by one or more remote clients and running programs on behalf of remote clients.