spin-trigger-mqtt VS spin

The MQTT trigger is a feature of the Spin framework that allows a Spin application to subscribe to a specific MQTT address. Individual components within that application can then be configured to monitor particular topics at the address. When messages are detected on these topics, the corresponding component functions are triggered.

Let’s start by looking at the implementation of our first component, which is triggered by messages published to an MQTT topic and persists the data in a SQLite database. It is implemented in Rust and was scaffolded using the MQTT template. In the Spin application manifest (spin.toml), we are using a Spin application variable to dynamically configure the address for the MQTT broker. This will enable us to set Spin to connect to a broker at "mqtt://localhost:1883" when running locally and at "mqtt://emqx.default.svc.cluster.local:1883" when running in SpinKube. We also set the keep alive interval (secs) for connections with the broker and username and password authentication credentials. In this example application, the broker does not require authentication, so the credentials are left empty.

Before WASIp2 was even released, a few of us in the Bytecode Alliance were already prototyping the foundations of WASIp3, and we’ve made a lot of progress since then. Although there’s still significant work to do before it’s finally released later this year, we expect to start making release candidate snapshots available in the next couple of months, with experimental support for those snapshots landing in Spin and other popular runtimes soon after. These runtimes use WASI to provide a standardized environment for WebAssembly modules to interact with the host system.

spin CLI

Today, we are excited to announce that Spin has officially been accepted as a Cloud Native Computing Foundation (CNCF) Sandbox project and SpinKube will now be housed within the Spin project.

In the journey of discovering all possibilities in this mechanism, we look to enhance the DevEx when developing the Spin app on the local machine. To experiment with some innovation ideas, I have a look at .NET Aspire (just released a new version with .NET 9 a couple of months ago).

The MQTT trigger is a feature of the Spin framework that allows a Spin application to subscribe to a specific MQTT address. Individual components within that application can then be configured to monitor particular topics at the address. When messages are detected on these topics, the corresponding component functions are triggered.

Spin is an open-source framework for building WebAssembly applications, and has a ton of amazing features - including portability (a single binary can run on many architectures), and sub-millisecond (0.51ms) response times, which means an application can serve requests without any noticeable delay or cold start. See our docs for more details.

Spin is the open source developer tool for building WebAssembly applications. Spin comes with batteries included to build reactive WebAssembly applications (we often call them Spin apps). Spin is language-agnostic, so you can choose from a wide range of programming languages to build your Spin apps. Spin guarantees portability across different operating systems and architectures, strict sandboxing, and incredible sub-millisecond cold start times. Check out the project documentation to dive deeper into Spin.

The Spin community is proud to introduce Spin 3.0 — the latest major release of Spin, the open source developer tool for building, distributing, and running serverless WebAssembly (or Wasm) applications everywhere.

And how fast is this? Different Serverless platforms have different speeds. With Spin, the handler can be started in under a millisecond. That is why there is no reason to run a server. If we can start this fast, it's much more efficient (and much cheaper) to not be running idle servers.

Wasm apps written using Spin apps follow a design pattern called serverless functions in which the app is started once when a request comes in. The app handles the request and then shuts down. If four requests come in simultaneously, then four copies of the app are started. When zero requests come in, no copies of the app are running. They are, in this sense, “zero cost”.