Cloud Snapshot Migration for Instance Termination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud computing environments, applications face challenges due to abrupt termination of computing instances by third-party systems, leading to data loss, and the need for overprovisioning based on peak memory requirements, resulting in inefficient resource allocation and increased costs.

Innovation Solution

Implementing a snapshot management system that captures baseline and delta snapshots of application states, allowing for seamless data migration between computing instances, optimizing resource allocation by dynamically reallocating resources based on current needs and reducing costs by using instances with appropriate memory and processing capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a computing instance is allocated to an application based on peak memory requirements, then the application can complete all processing phases, but the cost increases due to overprovisioning for phases that do not require maximum memory

Engineering Contradiction:
Improvememory capacityVSAvoidcost
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent segments the application execution into different phases with varying memory requirements. Instead of allocating maximum memory for all phases, the system allocates memory based on the specific phase being executed. The memory management module tracks which phases have completed and allocates appropriate memory resources for current phases, allowing the application to progress through phases with optimized resource allocation.

Inventive Principle:
Principle #1Segmentation

2Productivity

If a third-party system terminates a computing instance abruptly, then resource reallocation can occur quickly, but data loss occurs because the application cannot save its state

Engineering Contradiction:
Improveresource allocation speedVSAvoiddata loss
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent implements preliminary action by having the application continuously save its state to persistent storage before termination occurs. The memory management module ensures that the application's current phase, progress, and data are periodically committed to disk or a persistent database. This preliminary saving action ensures that even if the computing instance is abruptly terminated by a third-party system, the application can resume from the last saved state without data loss.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If the computer company terminates access to a computinginstance without notice, then demand response can be maintained, but the application cannot extract or save its process state in time

Engineering Contradiction:
Improvedemand responseVSAvoidstate extraction time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent ensures continuity of useful action by implementing continuous state saving and phase tracking. The memory management module continuously monitors which phases have completed and maintains an updated record of application state in persistent storage. This continuous action ensures that the application state is always current and can be immediately extracted or restored, eliminating the time loss problem when termination occurs without notice.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS12141041B2Efficiency and reliability improvement in computing service
Publication Date: 2024.11.12 MEMVERGE INC
  • US12141041B2 patent drawing
  • US12141041B2 patent drawing
  • US12141041B2 patent drawing

AI summary

To address loss of access to computing instances in a cloud computing environment, techniques are introduced for moving an application between computing instances in the cloud computing environment. A computing service captures baseline or delta snapshots of the state of the application running on a first computing instance. A baseline snapshot is indicative of the full state of the application, and a delta snapshot is indicative of changes in the state since a most recent snapshot was captured. Responsive to receiving an indication that the first computing instance is to stop servicing the application, the computing service stops the application from running on the first computing instance and moves data from the captured snapshots to a second computing instance. The computing service resume execution of the application on the second computing instances and captures snapshots of the state of the application at the second computing instance.