Announcing Spin 2.4

spin webassembly wasi component model release wasmtime

Spin applications have always been able to make requests to other components in the same application (“self-requests”). This effectively makes Spin applications a set of connected microservices. In Spin 2.2, we streamlined this by adding support for sending self-requests by route, avoiding the need to specify a hostname, port, or protocol. With Spin 2.4, we’re introducing support for application-internal service chaining. Now, if you opt-in, applications will enforce that requests between components within the application are handled in the same process. This removes some key sources of complexity for distributed applications, namely infrastructure-induced partial failures and unpredictable latency.

What Spin 2.4 adds is the ability to ensure - at deploy time - that the runtime environment will handle these self-requests internally, turning it into something that the developer can rely on as part of the application’s architecture. This means that developers can benefit from microservice patterns, language flexibility, and smaller components without accidentally building a distributed application and all of the complexity that comes with it.

Leave a Comment