Composing Components with Spin 2.0

Composing Components with Spin 2.0

Over the past few years, WebAssembly (Wasm) has become an exciting new target for applications. Its small binaries, polyglot bytecode, and fast startup times make it a wicked unit for serverless applications. From the start, Spin aimed to make it easier for developers to get started using Wasm and take advantage of each advance in the technology. With Spin 2.0, we have unlocked an exciting evolution of Wasm, the component model. This blog walks through how to take advantage of components in Spin 2.0.

WebAssembly, WASI, and the Component Model

WebAssembly, WASI, and the Component Model

WebAssembly has evolved to support many languages and environments beyond browsers, enhanced by WASI for system interactions, and is utilized in Fermyon's Spin platform for serverless functions.

Wasm, WASI, Wagi: What are they?

Wasm, WASI, Wagi: What are they?

Any new technology comes with a litany of new terminology. WebAssembly is no different. In this post, we take a look at how Wasm (short for WebAssembly), WASI (the WebAssembly System Interface) and Wagi (WebAssembly Gateway Interface) work together. The Fermyon Spin framework makes use of all three of these.

Introduction to WebAssembly on the Cloud

Introduction to WebAssembly on the Cloud

WebAssembly may have started as a browser technology, but it has moved outward. One hugely promising space for WebAssembly is in the cloud. Its security, speed, size, and flexibility make it a great basis for building cloud services.

🔥 Recommended Posts