Event-Driven Replication for Computing Resource Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Migrating computing resources from one network to another is challenging due to the difficulty in managing changes and downtime, especially when resources are actively performing tasks, as existing methods require stopping and testing resources at different hosts, which is time-consuming and complex.

Innovation Solution

Implementing event-driven replication, which captures changes to computing resources over time, replicates data to a destination network, and formats it for seamless migration, minimizing downtime by continuously updating the resource state and converting it for the new environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing migration methods are used to migrate computing resources, then the resources can be moved from one network to another, but the migration process requires stopping and testing resources at different hosts which causes significant downtime and operational disruption

Engineering Contradiction:
Improveresource availability during migrationVSAvoidmigration downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by creating a replica of the computing resource in the destination network before the actual migration occurs. The replica is kept synchronized with the original resource through continuous replication of data blocks, so that when migration is initiated, the resource can be quickly switched to the destination with minimal downtime.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy (replica) of the computing resource in the destination network. This replica contains copies of data blocks from the original resource and can be activated to take over workloads. The copying approach allows the original resource to remain operational while the replica is being prepared, enabling seamless failover.

Inventive Principle:
Principle #26Copying

2Productivity

If computing resources are actively performing tasks during migration, then continuous operation is maintained, but managing changes and synchronizing data between source and destination becomes complex and difficult

Engineering Contradiction:
Improvecontinuous operation during migrationVSAvoiddata synchronization complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the data storage into discrete data blocks that can be independently tracked and replicated. Each data block has an identifier that allows the system to monitor which blocks have been replicated and which need updating. This segmentation simplifies the complexity of synchronizing actively changing data by breaking it into manageable units.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements feedback mechanisms where the replica continuously monitors and detects changes to data blocks in the original computing resource. When changes are detected, the system automatically replicates the updated blocks to the replica. This feedback loop ensures synchronization without requiring complex manual management, allowing continuous operation during migration.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If traditional migration approaches are used, then resources can be migrated between networks, but the process is time-consuming and requires manual intervention for testing and validation

Engineering Contradiction:
Improveresource migration capabilityVSAvoidmigration process simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system enables self-service migration where the replica automatically detects changes, replicates data blocks, and can be activated to take over workloads without extensive manual intervention. The automated change detection and replication processes eliminate the need for manual testing and validation steps, making the migration process simpler while maintaining adaptability across different networks and resource types.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10754741B1Event-driven replication for migrating computing resources
Publication Date: 2020.08.25 AMAZON TECH INC
  • US10754741B1 patent drawing
  • US10754741B1 patent drawing
  • US10754741B1 patent drawing

AI summary

A migration system or service may implement event-driven replication for migrating a computing resource from a source network to a destination network. A replication event may be detected to obtain a state of a data volume for a computing resource hosted in a client network. A request to a replication agent hosted in the source network may instruct the replication agent to copy at least some of the data of the data volume and send the data to the destination network. The migration service may generate a state of the data volume from the received data in a format that is operable to host the computing resource in the destination network and store the generated state of the data volume.