6 posts tagged with "WASI"

Cloud Native Wasm Day (co-located with KubeCon + CloudNativeCon EU, 2024) is always a great event but this year was a little different. In 2024, discussions are turning from theory towards working with Wasm in practice, with companies in a variety of sectors sharing their experiences.

What's particularly exciting for us, as CNCF wasmCloud maintainers, is how quickly wasmCloud is being adopted. So many of this year's talks come from companies already working with wasmCloud; many in production. We've summarized all the talks from this year's event and recommend paying particular attention to presentations from wasmCloud community users Orange and Machine Metrics.

From the beginning, wasmCloud has used zero-trust architectural patterns and Wasm's intrinsic isolation to deliver secure-by-default distributed computing. Our security posture was validated in an October 2023 audit from OSTIF and Trail of Bits, where we received excellent marks. It's important, however, that our approach to security is not only robust and default, but extensible.

With wasmCloud 1.0, our flexible, pluggable policy service API integrates easily with standard cloud native tooling like Open Policy Agent. As you take wasmCloud to production, operators can use the tools they're already using to extend and tailor the platform's already-deep security.

Observability is a cornerstone of any cloud native system. With v1.0, wasmCloud supports the three pillars of observability—traces, logs, and metrics—using the industry-standard OpenTelemetry (OTEL) specification.

WebAssembly is bringing us closer than ever to a world of "write once, run anywhere." From developer platforms to the browser to embedded devices, Wasm gives us a way to write portable, efficient, sandboxed code. The WebAssembly System Interface (WASI) and the Component Model extend the power of WebAssembly with standard APIs for core functionalities like HTTP, CLI, I/O, and more—as well as a specification for compiling Wasm applications as interoperable, composable components.

Now, wasmCloud 1.0 brings the Component Model and the standard APIs of WASI 0.2 to production-grade distributed computing. By embracing community standards, wasmCloud ensures that your business logic is truly vendor-neutral. Components built for wasmCloud 1.0 run anywhere that supports WASI 0.2, and any component you've built to target WASI 0.2 is ready to run distributedly with wasmCloud.

We’re proud to announce wasmCloud 0.82—the last stop on the road to our 1.0 milestone. This release is all about preparing the way, bringing:

• Full and stable support for WASI 0.2 APIs
• Quality-of-life improvements for builds and deployment
• Support for OpenTelemetry logging
• Additional bug-fixes and improvements

WASI Preview 2 officially launched! After a vote in the WASI Subgroup of the W3C WebAssembly Community Group, the standard set of interfaces included in the launch of Preview 2, aka WASI 0.2.0, is ready for use by library implementers. We've been closely tracking the different release candidates of WASI 0.2.0 over the last 6 months, and wasmCloud will update its runtime WIT definitions to the pinned versions in just a few days.