Redundant Cloud Management Stacks for Parallel API Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In hybrid cloud environments, user operations can fail or be delayed due to errors in the cloud management stack, particularly under high system loads, as the cloud management stack may fail to update correctly, leading to interruptions in user operations.

Innovation Solution

Implementing redundant cloud management stacks that process duplicate API calls in parallel, ensuring that at least one API call is successfully processed and the corresponding operation is performed, even if one stack experiences an error, thereby reducing the likelihood of user operation failures and improving user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single cloud management stack is used to manage hybrid cloud environments, then the system structure remains simple, but user operations may fail or be delayed under high system loads due to errors in the cloud management stack

Engineering Contradiction:

Improveuser operation success rateVSAvoidcloud management stack structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements redundant cloud management stacks specifically for processing duplicate API calls, rather than duplicating the entire cloud management system. This localized redundancy focuses the quality improvement on the critical path of user operations while maintaining simplicity in other areas of the system architecture.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system proactively creates duplicate API calls that are processed in parallel by redundant cloud management stacks before the original operation completes. This cushioning mechanism ensures that if the primary stack fails, a backup operation is already in progress, preventing user operation failures without requiring complex post-failure recovery procedures.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If redundant cloud management stacks process duplicate API calls in parallel, then user operation failures are reduced, but system complexity and resource consumption increase

Engineering Contradiction:

Improveoperation completion reliabilityVSAvoidcloud management stack configuration

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates simplified copies of API calls rather than duplicating entire cloud management stacks. These duplicate calls are processed in parallel by redundant stacks, providing fault tolerance through copying the essential operational data and logic without replicating the full system complexity.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system merges the results from multiple parallel processing paths by selecting the successful operation outcome. When duplicate API calls are processed in parallel, the system combines these paths and selects one successful result, reducing the complexity of managing multiple independent systems while maintaining reliability benefits.

Inventive Principle:

Principle #5Merging (Combining)

3Productivity

If duplicate API calls are processed in parallel by redundant stacks, then operation speed is improved, but resource consumption increases

Engineering Contradiction:

Improveoperation processing speedVSAvoidcomputational resources

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The system processes duplicate API calls in parallel only for critical operations where speed and reliability are paramount, rather than duplicating all system operations. This partial action approach applies parallel processing selectively to high-priority tasks, improving productivity for critical operations without unnecessarily consuming resources for less important functions.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

Duplicate API calls are initiated in advance and processed in parallel before the system needs to respond to the user. This preliminary action allows the system to prepare multiple operation paths simultaneously, then select the successful result, effectively increasing processing speed without the continuous resource overhead of maintaining parallel systems ready at all times.

Inventive Principle:

Principle #10Preliminary action

4Loss of energy

If only one processed duplicate API call is performed while others are not performed, then resource waste is reduced, but the benefit of parallel processing is limited

Engineering Contradiction:

Improvecomputational energy wasteVSAvoidfault tolerance capability

Core Design Contradiction:

Loss of energyVSReliability

Solution Approach 1:

The system extracts and processes only the essential operational outcome from multiple parallel duplicate API calls, rather than executing all duplicate operations. By taking out just the successful result and discarding redundant executions, the system reduces energy waste from duplicate operations while maintaining the reliability benefits of having multiple processing attempts in parallel.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS11102278B2Method for managing a software-defined data center implementing redundant cloud management stacks with duplicate API calls processed in parallel

Publication Date: 2021.08.24 VMWARE INC

AI summary

A method for managing a software-defined data center is disclosed. The method involves implementing redundant cloud management stacks, processing duplicate application program interface (API) calls in parallel with the redundant cloud management stacks, and performing a data center operation corresponding to the processed duplicate API calls.