Container Orchestration Service Auto-Termination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed computing environments, such as cloud provider networks, failed software deployments can lead to the wastage of computing resources as existing systems do not efficiently detect and terminate failed deployments, resulting in prolonged resource utilization and poor user experience.

Innovation Solution

An orchestration service is implemented that automatically detects failed deployments and rolls back to a previous healthy state, utilizing a deployment manager to monitor conditions and terminate failed deployments, thereby reducing resource expenditure and improving user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system continuously attempts to execute failed user code, then the deployment process continues running, but computing resources are wasted and user experience deteriorates

Engineering Contradiction:
Improvedeployment success rateVSAvoidcomputing resource wastage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary detection of deployment failures by monitoring execution conditions and outcomes. When a failure is detected, the system proactively terminates the deployment process before it can continue consuming computing resources, thus preventing resource wastage while maintaining deployment reliability through early intervention

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism that continuously monitors deployment execution status and provides real-time information about failure conditions. This feedback loop enables the system to detect failures, make termination decisions, and adjust deployment processes dynamically, resolving the contradiction between continuing deployment attempts and preventing resource wastage

Inventive Principle:
Principle #23Feedback

2Loss of time

If the system detects and terminates failed deployments quickly, then computing resource wastage is reduced, but system complexity increases due to monitoring and detection mechanisms

Engineering Contradiction:
Improvedeployment failure detection timeVSAvoidorchestration service complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The orchestration service implements self-service capabilities by automatically monitoring its own deployment processes, detecting failures, and terminating unsuccessful deployments without external intervention. This self-monitoring and self-correction mechanism reduces detection time while managing complexity through automated rather than manual processes

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system merges the detection, monitoring, and termination functions into the existing orchestration service infrastructure. By integrating these failure detection capabilities with the deployed application code itself rather than adding separate external monitoring systems, the solution reduces detection time while minimizing the increase in overall system complexity

Inventive Principle:
Principle #5Merging (Combining)

3Ease of operation

If the system rolls back to previous healthy state upon failure, then user experience is improved, but additional computing operations are required

Engineering Contradiction:
Improveuser experienceVSAvoiddeployment efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system maintains previous healthy deployment states as a form of cushioning against future failures. When a deployment failure occurs, the system can quickly restore to the pre-prepared previous state, improving user experience by ensuring service continuity. This pre-positioning of rollback targets balances the need for quick recovery with deployment efficiency

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS11797287B1Automatically terminating deployment of containerized applications
Publication Date: 2023.10.24 AMAZON TECH INC
  • US11797287B1 patent drawing
  • US11797287B1 patent drawing
  • US11797287B1 patent drawing

AI summary

Generally described, the present application relates to providing a container orchestration service (“service”) that can automatically detect and terminate a failed deployment and automatically roll back to a previous healthy deployment. For example, the service may receive a request to deploy a new user code onto one or more compute instances usable to execute the new user code, where the new user code is an updated version of an old user code to be replaced by the new user code. The service may then attempt to execute a plurality of instances of the new user code on the one or more compute instances, determine, prior to replacing all instances of the old user code to be replaced by the plurality of instances of the new user code, that the deployment of the new user code has satisfied a failed deployment condition, and terminate the deployment of the new user code.