Marine runs multi-module WebAssembly applications with interface-types and shared-nothing linking scheme
Go to file
2020-12-17 22:35:50 +03:00
.circleci i64 -> i32 for 'target' in log_utf8_string (#49) 2020-12-17 18:46:01 +03:00
.github/workflows i64 -> i32 for 'target' in log_utf8_string (#49) 2020-12-17 18:46:01 +03:00
aquamarine-vm depend on the master branch of stepper-interface 2020-12-17 22:35:50 +03:00
crates initial (#45) 2020-12-02 02:08:54 +03:00
engine Use Vec<u8> instead of String for data (#51) 2020-12-17 21:24:42 +03:00
examples i64 -> i32 for 'target' in log_utf8_string (#49) 2020-12-17 18:46:01 +03:00
fluence-app-service Use Vec<u8> instead of String for data (#51) 2020-12-17 21:24:42 +03:00
fluence-faas Use Vec<u8> instead of String for data (#51) 2020-12-17 21:24:42 +03:00
images Update readme (#43) 2020-11-12 16:25:47 +03:00
tools Use Vec<u8> instead of String for data (#51) 2020-12-17 21:24:42 +03:00
.gitignore update config.yml 2020-12-01 11:49:49 +03:00
.rustfmt.toml add rustfmt config 2020-06-03 23:08:26 +03:00
Cargo.lock depend on the master branch of stepper-interface 2020-12-17 22:35:50 +03:00
Cargo.toml update examples (#47) 2020-12-09 15:57:10 +03:00
LICENSE add license and readme 2020-05-02 12:44:49 +03:00
README.md update readme 2020-12-10 17:07:58 +03:00

Fluence Compute Engine

FCE is a general purpose Wasm runtime that could be used in different scenarios, especially in programs based on the ECS pattern or plugin architecture. It runs multi-module WebAssembly applications with interface-types and shared-nothing linking scheme.

Fluence nodes use FCE to execute aquamarine and services compiled to Wasm:

fluence stack

At now, it is in the heavily developing phase, more detailed information could be found in docs