We’re excited to be heading to Austin next week for the North America iteration of Civo Navigate! Building on top of our presence at Civo Navigate in London back in September, we’re coming back as Platinum sponsors, with a workshop and talk to top it all off. Be sure to read on to find out where we’ll be each day.
Today, we are happy to announce Spin 2.2, which includes the following enhancements to Spin:
- Support for the new stable WASI 0.2.0 via Wasmtime 17
- Support for multiple trigger types in a single Spin application
Let’s have a look at a few of the highlights of the release!
Today we’re excited to announce support for linking Spin applications to custom key value stores on Fermyon Cloud. With
spin cloud version 0.7.0 or newer, application developers can link their applications to their desired key value stores during deployment. Developers can later change which stores are linked to the application without the need to recompile or redeploy their source code.
In Segment 1 we introduced you to the overall concepts behind High Performing teams, some background about the authors and the highest level outline of this practical guide to building High Performing teams.
In this Segment we talk about the most essential effort that must occur before you coalesce your founding team or hire your first person. If you’ve already coalesced your founding team, stop immediately, do this exercise and be prepared for the potential that the exercise might change the makeup of this founding team.
With the release of Spin 2.0, Spin now supports WebAssembly (Wasm) components natively. In a recent blog post, Kate Goldenring wrote about how composing applications using components is now possible, go check out that post as a good addendum to what you’re about to read here.
As a TL;DR, what Kate focused on describing is the scenario, where you want to add functionality to your components, by composing in other components. Specifically, Kate wanted to outsource the responsibility of authorizing the caller to the business logic she implemented, to a separate component.
In many ways, what the Wasm Component Model (component model from now on) enables, is to delegate responsibilities to implementations made by others. This is in no way foreign to what we do on a daily basis, by importing libraries in our source code, building container images based on layers provided by others, hosting our applications on operating systems we didn’t build, and so on and so forth. Matt recently covered how the component model impacts the scenario of using libraries at development time.
In this blog post, I’ll dive deeper into what the component model can do for platform builders and platform engineers to take on more responsibility, by showing how the interfaces provided by platforms to developers, can be at much higher abstractions than what we are used to today.
Server-side WebAssembly (Wasm) applications built with Spin can run anywhere. The ability to run Spin applications on any processing architecture and operating system is a big benefit, stemming from using WASI through Wasmtime as the runtime for Spin.
In most scenarios today, we rarely run processes directly on a server, e.g., through a shell or using a service daemon like systemd. For the platforms we run, there are typically highly sophisticated schedulers involved, to ensure availability with multiple servers, and ease of scaling for more dynamic workloads.
Implementations of the suite of Open Container Initiative (OCI) specifications and Kubernetes (K8s), are highly adopted across public cloud providers, and in private data centers, to help solve the above. This means that for Spin to fulfill its promise of being portable across any platform, it is important that Spin also has a story for being part of the eco-system around OCI and K8s.
At Openshift Commons back in October 2023, we announced support for Spin on Red Hat Openshift. You can watch the video of that talk here and see the slides here. This blog was slated to go out in the months there-after but was lost into the holiday madness. So without further delay, we want to publicly announce support for Openshift for WebAssembly with Fermyon Spin.
Back in December we launched Advent of Spin 2023 and said “’Tis the season to learn something new”. We put together a series of weekly challenges designed to test your Spin mettle. We enjoyed seeing your submissions across 4 challenges involving a list of presents, generating Christmas stories using AI, filling knapsacks with gifts, and even solving a fun little number game.
Overall, we had many great submissions for the 4 challenges. Here are some of the amazing submissions we received for the four Challenges in Advent of Spin 2023.
From Day One, Fermyon has had several core, long-term objectives, one of which is to create a company that employees would describe as the best place to work, EVER. This past year (2023) we secured #9 on the Will Reed Top 100 List for startups.
That inspired us to share more broadly how we think about high performing startups. A few of the leadership team began the development of an approach and system for building great companies during their time together at three previous start-ups. Now, at Fermyon they are documenting and implementing the system they refined over that time.
This article delves into using Python for solving mathematical problems over the web. We provide hands-on Python examples, compiled to WebAssembly (Wasm) and showcase how easy it is to use Python libraries to create Wasm-powered serverless applications. We also provide instructions on deploying to Fermyon Cloud and make the examples in this article accessible, for you, via the web.