bytecodealliance / bytecodealliance/wasmtime

Migrating workloads - snapshot and restore somewhere else

Open
#4,002 2 comments 6 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
18.6k
Forks
1.8k
Avg merge
1d 18h
Merged PRs (30d)
126

Description

#### Feature

When running a module with wasmtime, I would like to be able to capture the running memory of a workload, perhaps, while running, pause or stop the workload, move the workload elsewhere, then start the workload from where it left off.

#### Benefit

Being able to migrate a workload would enable workload state to be transferred to compute as the user of the workload is moving. Imagine someone driving down the highway and the workload traveling along edge compute with the user.

#### Implementation

Todo if the feature is interesting to the project.

#### Alternatives

One alternative is to externalize state from the module through some stateful service / component interface. However, this would require module developers to take a dependency on some service interface and rebuild applications to integrate with this external state store.

/cc @squillace

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.