Component Model in Software Defined Vehicles
summary
Component model moves application parts from cloud to microcontrollers and demonstrates a canonical ABI lifting/lowering flow that copies ownership-safe strings between sandboxes, then a symmetric ABI that removes the runtime hop for shared-memory binaries. A working prototype (native async calls, vasi 0.2 mapping) and a wasm-tools fork exist on GitHub, deployed experimentally a year ago with debugging pain but functional output. Notes include need for zero-copy shared memory and flat data types for safety-critical high-throughput sensors.
AI-written summary · about
chapters (17)
- 0:00Component model in SDVs
- 1:04Hardware architecture in SDVs
- 2:30Classical containers limitations
- 3:36WebAssembly components advantages
- 5:25Component model example
- 7:55Language-neutral interface definition
- 9:00Canonical ABI explained
- 16:16WebAssembly to native transition
- 17:39Optimizing native binaries
- 18:25Mixing languages with components
- 20:35Simplified API for native binaries
- 22:00Symmetric ABI for shared setup
- 25:31Embedding WebAssembly with ABI
- 26:37Zero-overhead plugins
- 27:43C++ challenges in components
- 28:23Async calls prototype
- 29:05Future directions
related talks
38mTowards a Component Model 1.0
31mWebAssembly Component Model: Enhancing Security, Productivity, and...
27mDoes the Component Model Require Extra Copying?
30mKeynote: What is a Component (and Why)?
16mThe nuts and bolts of WebAssembly's component model
08mKeynote: WASI Standards and the Component Model: Transforming Application Development Forever
52mWhat is a WebAssembly component (and why?)
26mKeynote: The Path to Components