Beyond HTTP Microservices with Spin
summary
Spin is extendable beyond HTTP: the runtime splits into two processes (loader and spin trigger) and custom triggers must be written in Rust using the spin core and spin trigger crates. The demo builds a TCP line trigger that reads one line over TCP, registers it with spin via spin pluginify and spin plugin install, loads the spin.lock application object, and dispatches to a Wasm guest. It runs on port 8089, returns a telnet response and even fetches a dog fact from the standard Fermi on demo API while warning to avoid unwraps and use structured termination reasons.
AI-written summary · about
chapters (16)
- 0:00Intro
- 8:33Rust Trigger
- 12:50Incantations
- 13:35Trigger Executor
- 14:15Run
- 16:30Trigger Mapping
- 17:15Trigger
- 17:45New
- 18:40Running
- 20:30Socket Binding
- 21:45Guest Code
- 23:15Telnet
- 24:25Source schema
- 24:55Wrapup
- 25:30Questions
- 26:20Conclusion
related talks
19mTaking WebAssembly for a Spin
59mNext generation microservices and serverless apps with WebAssembly & Spin
30mCloud-Native vNext with WebAssembly and Spin
25mBreaking the Latency Barrier: Tackling Compute and Network Delay With Globally Distributed Wasm
23mWhat is Cloud Native WebAssembly?
01h 34mTutorial: Getting Started with Serverless WebAssembly and Spin
01h 03mTruly Portable Code: Serverless WebAssembly in a Distributed World
25mBuilding Serverless AI Apps with Spin and WebAssembly