Golem Cloud - powered by WebAssembly
summary
Golem Cloud uses the WebAssembly Component Model to provide transparent durable execution by recording non‑deterministic host calls into an oplog, replaying them to restore state; full VM snapshots are prototyped but not yet shipped, and Custom snapshotting requires user save/load hooks. Workers are durable or ephemeral, RPC currently uses a custom host interface with a planned migration to wrpc, and tooling includes the rib scripting language and an app manifest build/composition system.
AI-written summary · about
chapters (16)
- 0:00Golem Cloud and WebAssembly
- 1:03Why WebAssembly for Golem
- 4:59Transparent durability with oplog
- 7:06Durable vs ephemeral workers
- 7:50Component model and invocation
- 9:15Worker communication with RPC
- 13:51Dynamic linking and RPC client
- 15:55Persistent sockets and streaming
- 17:18Worker communication permits
- 18:20Host APIs and WebAssembly interfaces
- 19:25WebAssembly ecosystem contributions
- 20:09RIB scripting language
- 22:44App manifest for components
- 24:52Golem RDBMS package
- 25:35Wish list for WebAssembly
- 27:27Q&A: Actor framework?
related talks
20mGolem and the WASM Component Model
40mWebAssembly - The Future of Distributed Computing
13mLightning Talk: Wildly Distributed Programming: Wasm and the Future of Distribute...
32mCloud Native Apps with Server-Side WebAssembly
29mwasi-cloud: The Future of Cloud Computing with WebAssembly
28mWebAssembly VM in Nock
50mWeb Assembly
31mFrom Napkin to the Cloud: A WebAssembly Journey