Cosmonic Blog

One of the most formidable barriers in adopting and building event-sourced systems is learning to live with, and even embrace, the restrictions on component behavior. As it turns out, the same restrictions that make WebAssembly so powerful line up perfectly with event sourcing requirements.

• Netreap takes Cilium beyond Kubernetes – open source and operational in Nomad
• Remedies Kubernetes edge trials – Nomad + Cilium create ideal conditions for Wasm at the edge

ARLINGTON, Virginia. May 23, 2023. Cosmonic, creator of the Cosmonic WebAssembly (Wasm) PaaS and active contributor to CNCF sandbox project wasmCloud, has open sourced Netreap, an application designed to allow the deployment of Cilium as a container network interface (CNI), outside of Kubernetes, in HashiCorp Nomad workloads. The move brings Isovalent Cilium (a CNCF incubation project) together with Nomad to create the ideal toolset for running WebAssembly (Wasm) applications in multiple clouds, on bare metal and on the smallest devices at the far network edge.

In our last post we built an deployed a service with Rust and deployed it to Cosmonic's free infrastructure. In this post we'll build a React frontend to interact with the service.

Earlier this year, alongside our friends at DevPost, we launched the Cosmonic Distributed WebAssembly Hackathon and encouraged you all to get creative with Wasm and the Cosmonic platform.

We asked you to take your ideas, whether something that would improve your daily work, something that could replace functionality in an existing application, or be the beginnings of a potential startup and implement them using WebAssembly, hosted on Cosmonic.

We saw hundreds turn out to build hacks, side hustles and creative ideas on Cosmonic, and to snag a share of our $4,500 prize pot -- and we weren't disappointed!

One of the many things that Cosmonic makes incredibly simple is building and deploying services. In this post, we'll show how easy it is to build a service from scratch, and how a service can shift from monolith to globally distributed function at runtime without rebuilding.

In our last post, we looked at some of the challenges inherent in running a highly distributed, microservices-centric infrastructure and how to overcome issues of networking and security in this novel environment.

In particular, we looked at some of the limitations Kubernetes has, especially at the edge, and why this was a key reason for selecting HashiCorp Nomad as our container orchestrator for WebAssembly and wasmCloud.

Some thoughts and reflection on my first day using Wasm components for something more involved than hello world.

Every year, twice a year, we're lucky enough to see the latest and greatest in Cloud Native Wasm in one jam-packed day. This year we had the pleasure of traveling to Amsterdam for the EU circuit of KubeCon. Knowing that not everyone would be able to fly out to catch the event, we sponsored the recordings so that all of this great content would make it onto YouTube after the event. We've been attending WasmDay at CNCF KubeCon since the first one, and we wanted to share our insights with you for each talk, including a high level summary, some space for opinions, and then eventually the embedded recording once available.

• Cosmonic Connect allows third party integration with popular technologies and infrastructure
• Cosmonic Connect Kubernetes launches at KubeCon EU
• Introducing wadm: familiar, declarative application management for wasmCloud apps

This post will outline the reasons why Nomad is an ideal container orchestrator for WebAssembly and wasmCloud, and how we created Netreap to run Cilium in our Nomad clusters alongside the rest of our infrastructure. In my next post, I'll walk you through how to run Cilium on a Nomad node, and how Netreap performs in practice.