Application Migration Service for Cloud Transition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of existing enterprise-based network applications makes application migration to cloud computing environments a time-consuming, error-prone, and risky process, due to the need for careful management of virtual machine instances, resource monitoring metrics, and performance metrics across different server environments.

Innovation Solution

An application migration service that uses API requests to obtain private subnet information, dependency information, and resource monitoring metrics to select appropriate virtual machine instance types and host server types within a cloud computing environment, facilitating efficient migration and deployment of applications by matching resource usage with performance metrics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual application migration is performed from enterprise-based network to cloud environment, then applications can be moved to cloud computing resources, but the process becomes time-consuming and error-prone due to complexity of managing virtual machine instances and resource metrics

Engineering Contradiction:
Improveapplication migration speedVSAvoidmigration error rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces an application migration service as an intermediary system between the enterprise-based network and cloud computing environment. This service automatically manages the complex tasks of migrating virtual machine instances, monitoring resource metrics, and configuring cloud resources, thereby reducing both the time required and the potential for human errors in the migration process

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The migration service enables self-service automation by automatically discovering dependencies between applications and virtual machine instances, monitoring resource usage metrics, and performing migrations without requiring manual intervention for each step. The system autonomously handles the complex coordination required for successful migration

Inventive Principle:
Principle #25Self-service

2Manufacturing precision

If comprehensive resource monitoring and performance metric tracking are implemented during migration, then migration accuracy and resource optimization improve, but the complexity of managing migration processes increases

Engineering Contradiction:
Improvemigration accuracyVSAvoidmigration management complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The application migration service performs multiple functions within a single unified system: it discovers dependencies between applications and virtual machine instances, monitors resource usage metrics, selects appropriate cloud resources, and executes migrations. This multi-functional approach consolidates complexity into a manageable service rather than requiring separate tools for each task

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system continuously monitors resource usage metrics and performance data during the migration process, using this feedback to dynamically adjust migration decisions and resource allocation. This feedback mechanism ensures high migration accuracy by making real-time adjustments based on actual system state

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9811365B2Migration of applications between an enterprise-based network and a multi-tenant network
Publication Date: 2017.11.07 AMAZON TECH INC
  • US9811365B2 patent drawing
  • US9811365B2 patent drawing
  • US9811365B2 patent drawing

AI summary

A method of migrating applications from an enterprise-based network to a multi-tenant network of a compute service provider may include receiving a request to migrate an application running on a first virtual machine instance within the enterprise-based network. Dependencies of the application may be determined by identifying at least a second virtual machine instance within the enterprise-based network, where the at least second virtual machine instance associated with the application. Resource monitoring metrics associated with hardware resources used by the first virtual machine instance and the at least second virtual machine instance may be received. The first and at least second virtual machine instances may be migrated from the enterprise-based network to at least one virtual machine at a server within the multi-tenant network based on the monitoring metrics, thereby migrating the application from the enterprise-based network to the multi-tenant network.