Skip to main content

· 4 min read

Customize your wash CLI with WebAssembly components and wash plugins

In wash v0.28, we introduced wash plugins: a simple system for extending the wasmCloud Shell (wash) CLI with WebAssembly components. Users can install plugins from OCI registries, local files, or over HTTP, then execute the plugin as a subcommand to wash. Plugin developers simply build a given piece of CLI functionality as a component.

In this post, we'll show you how to install your first plugin. In themselves, plugins represent powerful, versatile tools that will accelerate workflows and help developers tailor tooling to their needs. But wash plugins are also a great example of how modular CLIs can be implemented with WebAssembly—and how components can accelerate development across a team.

· 3 min read

wasmcloud incubation process

Hey wasmCloud Community!

We wanted to give you an update on our journey toward Incubating status with the Cloud Native Computing Foundation (CNCF). As long-time users might have noticed, the process is taking a little longer than we initially anticipated, but there's a good reason for the delay. The CNCF Technical Oversight Committee (TOC) has been hard at work streamlining the entire incubation process, and we're one of the first projects to go through the updated version. A smoother incubation process will be a huge win for the broader CNCF community, and we thought it would be worthwhile to highlight some of the benefits we've seen.

· 12 min read

Build a custom messaging provider for Discord bots

A couple weekends ago I found myself wanting to write a Discord bot: specifically, a simple bot that I could tag with a message to trigger some processing and a response message. As I started thinking about what this bot could do, I realized this was an excellent use-case for a provider: instead of writing a one-off bot, I could create a reusable provider that would make it trivial to build any Discord bot I wanted.

The Discord API is fully-featured and massive, but for such a simple use-case, it would be overkill to work from scratch every time you wanted to write a bot. With a custom provider, I could simply write a component in any language and then plug it in to my provider via a simple API.

In this post, I'll retrace my steps to implement the custom provider using the wasmcloud-messaging interface, and show you how you can use the provider to write Discord bots of your own.

· 6 min read

wasmCloud 1.0 Hackathon

With v1.0 in the wild, wasmCloud maintainers are hacking on some big ideas, putting the new release through its paces, and generally recharging their engineering mana with some wildly creative Wasm projects. In last week's community call, maintainers and WebAssembly community contributors shared some of what they've been working on, including...

  • An implementation of Llama 3 using Ollama on wasmCloud
  • Workspaces on Wasm—a workspace manager for components
  • A tool to automatically generate YAML manifests for Wadm from WIT
  • Go support for wRPC

The participants' accomplishments are incredible—many of these projects were up and running in just a day or two. As Brooks mentioned later, "We got ridiculous mileage just by using WIT and components."

· 5 min read

wasmCloud-operator)

SEATTLE, (Open Source Summit), April 16, 2024. In response to growing demand among engineers for more open and community-led ways to bring the benefits of WebAssembly (Wasm) to Kubernetes, Cosmonic has contributed its Kubernetes operator to the CNCF wasmCloud ecosystem. The wasmCloud-operator (formerly known as Cosmonic Connect Kubernetes), allows Kubernetes practitioners free and unfettered access to wasmCloud in their own Kubernetes clusters, deployed and managed with the tools they know and trust.

· 9 min read

Cloud Native Wasm Day EU, Paris

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.

· 4 min read

Extending Security with wasmCloud 1.0 and Open Policy Agent

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.

· 3 min read

Vendor-neutral apps with wasmCloud and WASI 0.2

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.