Blog

Cross-posted from the wasmCloud blog.

Cross-posted from the wasmCloud blog.

Cross-posted from the wasmCloud blog.

On September 18, we held the first wasmCloud Innovation Day—an all-day virtual event bringing together project maintainers, enterprise users, members of the broader WebAssembly community, and folks interested in learning more about Wasm and wasmCloud.

Cross-posted from the wasmCloud blog.

With wasmCloud, you can build applications out of WebAssembly components and pluggable, reusable capabilities, so you can focus on the core logic of your application and abstract away the rest, all using open source standards.

Cross-posted from the wasmCloud blog.

Building WebAssembly components in .NET/C# is easier than ever before. In this post, we'll take a look at the landscape of .NET tooling for components, explore how to get started today, and find out how easy it is to compile .NET/C# code to a component and run it on wasmCloud.

Cross-posted from the wasmCloud blog.

wasmCloud 1.2 officially closes out the remaining issues from the Q2 Roadmap! This is the first release since we adopted our new, accelerated release cadence, so expect to see some great changes—but not quite as many as wasmCloud 1.1.

This post originally appeared on the Cloud Native Computing Foundation (CNCF) blog.

Operating in the manufacturing sector has never been more costly. Exacerbated by high inflation, the cost of materials, fuel, shipping and labor have risen exponentially post-pandemic. In response, manufacturers are looking for ways to reduce maintenance costs, and improve production capacity. They’re doing this by putting advanced data analytics into production lines to better understand and optimize machine performance.

Cross-posted from the wasmCloud blog.

We're proud to announce the release of wasmCloud 1.1, including the feature most commonly requested by users: secrets support. In addition to secrets, the new release brings along a bevy of enhancements for enterprises, exciting new capabilities like Postgres, and first-class support for Go-based custom capability providers. Let's take a look at some of the highlights.

Cross-posted from the wasmCloud blog.

WebAssembly components are made for cloud native environments:

• As WebAssembly binaries, components are truly agnostic to OS and architecture.
• Teams can compile components from their language of choice, then combine and interoperate—across languages—with other components via standard APIs. It's like building blocks.
• Components are orders of magnitude more efficient than containers, setting the stage for major cost, speed, and sustainability improvements.

With components, teams can write code in the language of their choice and run it anywhere...including in places where even containers are impractical. If your organization is already using Kubernetes, it's easy to run components on your clusters with wasmCloud. In fact, wasmCloud can help you extend Kubernetes to tackle traditional challenge areas like multi-cloud and edge.

In this tutorial, you'll learn how to get started running WebAssembly components on Kubernetes in three simple steps. The whole process should only take about five minutes.

Cross-posted from the wasmCloud blog.

Suppose you're developing an application as a WebAssembly component, and you need access to environment variables—but your app will run in an environment where this is impossible. What do you do? The WebAssembly ecosystem provides a powerful command-line tool for this and similar use-cases called WASI Virt, enabling you to encapsulate components within other components and abstract away requirements, or otherwise consolidate your application.

In this blog, we'll explore how component virtualization works, when you might want to use WASI Virt, and how to get started.