SPIN IT! JUMPSTART YOUR WASM JOURNEY WITH FERMYON SPIN

Knowing about the potential and the impact of WebAssembly (Wasm) for serverless computing, we will dive deeper and see serverless Wasm in action. This talk guides you through patterns and practices for building serverless workloads with Fermyon Spin. Thorsten Hans addresses everyday developer tasks like routing, configuration management, and persistence. You’ll understand how to integrate Wasm into your distributed application architecture and interact with existing components. It’s time to jumpstart your WebAssembly journey and design distributed architectures for the next wave of cloud computing!

Transcript

1. SPIN IT! Thorsten Hans @ThorstenHans Cloud-Native Consultant Jumpstart your Wasm journey with Fermyon Spin
2. Consultant @ Thinktecture #Azure #Containers #CloudNative #Wasm thorsten.hans@thinktecture.com thinktecture.com thorsten-hans.com @ThorstenHans Microsoft MVP | Docker Captain Thorsten Hans
3. • Intro • Triggers & Outputs • Patterns & Practices • Conclusion Agenda
4. • Intro • Triggers & Outputs • Patterns & Practices • Conclusion Agenda
5. Fermyon Spin is: • A serverless runtime build using Wasm, WASI, and the WebAssembly Component Model (leveraging wasmtime internally) • A collection of SDKs for many popular languages • A super focussed developer tooling Intro Let’s get everybody on track! 🦀
6. With Spin we can build • Reactive applications that respect to the key pillars of Wasm • Fast: Near-native speed • Lightweight: Super small distributable units (Wasm Modules) • Secure: Sandboxed execution environment Intro Let’s get everybody on track!
7. Let’s meet Fermyon Spin Walk through the demo application Demo
9. • Intro • Triggers & Outputs • Patterns & Practices • Conclusion Agenda
10. • Intro • Triggers & Outputs • Patterns & Practices • Conclusion Agenda
11. • Spin provides triggers that the runtime uses to invoke our code • The runtime instantiates our Wasm Module and invokes our code • Currently, Spin provides the following triggers • HTTP • Publish / Subscribe Triggers & Outputs
12. Outputs allow our code to interact with the surrounding world • Databases (SQLite, MySQL & PostgreSQL) • Key-Value Storage (SQLite, Redis) • Publish / Subscribe (Redis Channels) • Outbound HTTP Triggers & Outputs
13. • Intro • Triggers & Outputs • Patterns & Practices • Conclusion Agenda
14. • Intro • Triggers & Outputs • Patterns & Practices • Conclusion Agenda
15. When building HTTP-based applications with Spin we must • specify a route on which Spin should invoke our code • Implement code for handling different HTTP request types Although Spin SDK is tiny, it simplifies building full-fledged HTTP APIs Patterns & Practices
16. Routing capabilities in HTTP-based Spin applications Demo
17. Regardless of whether we must invoke backend APIs or 3rd party endpoints, Outbound HTTP is an easy to grasp, yet important capability provided by the Spin SDK. Patterns & Practices Outbound HTTP
18. Outbound HTTP leveraging the Spin SDK Demo
19. Configurability is mission-critical when building software that is executed in different environments. Spin apps are no exception here. We must use proper mechanisms to deal with sensitive and non-sensitive configuration data. Patterns & Practices Configuration Management
20. • The Spin Manifest spin.toml is the center of gravity. All configuration aspects are defined here. • We use variables to specify non-sensitive configuration data • For sensitive configuration data, we can use HashiCorp Vault • We link HashiCorp Vault to our app using a runtime-config file Patterns & Practices Configuration Management
21. Configuration data for Spin apps Demo
22. • Publish is achieved using the Spin SDK • Constructing messages is up to us, which means we can modernize (read: replace containers) with ease, using cloudevents or by mimicking existing messages • When subscribing to messages, we must implement filters on our own Patterns & Practices Publish / Subscribe
23. Publish / Subscribe in distributed apps with Spin Demo
24. • Intro • Triggers & Outputs • Patterns & Practices • Conclusion Agenda
25. • Intro • Triggers & Outputs • Patterns & Practices • Conclusion Agenda
26. • With Spin, Fermyon demonstrates how WebAssembly will change the way we build software for the next wave of cloud-computing • We’re able to combine best from both worlds, Containers and WebAssembly to build distributed architectures for the upcoming years • Available Spin SDKs and plain WAGI support makes it super easy to get started (using any language that compiles to Wasm) Conclusion
27. • Hyperscalers want Wasm to drive hardware utilization, lift smaller application packages, get proper isolation and security in place and scale horizontally to and from 0 without facing the dilemma of cold-start times (Looking at you, Azure Functions *scnr*). • Application developers on the otherside had to tacklequite some pitfalls to adopt Wasm (SDKs., dev tooling, etc) • From my point of view, Fermyon is able to close the gap and drive Wasm adoption on the server and in the cloud to whole new level Conclusion
28. Thanks for your attention @ThorstenHans @Thinktecture