28 posts tagged with "Wasm"

By enabling cloud native back ends to run on operational edges, Wasm allows us to deploy business logic closer to users or data, even to places Kubernetes and containers can't go.

This article first appeared in InfoWorld as part of the New Tech Forum.

The Cosmonic wormhole exposes an HTTPS endpoint for your application that's accessible from outside of your constellation. Any actor with the HTTP Server capability can use a wormhole through Cosmonic's implementation of the HTTP Server provider. When you first create a wormhole, a randomly generated DNS name like fuzzy-lake-1234.cosmonic.app. These random DNS names are auto-generated; a couple of familiar words and numbers, designed to be unique but user-friendly, no long strings of random characters.

Collaboration, community, and diversity are the keys to technological innovation. This is why we are thrilled to announce that Cosmonic is involved in two adjacent events, set to revolutionize the WebAssembly (Wasm) landscape: The Linux Foundation's WasmCon and the Bytecode Alliance's WebAssembly Hackathon. Both events are being held near each other - WasmCon in Bellevue, WA on September 6 and 7, and “Componentize the World” on Friday September 8th in Redmond, WA.

Cosmonic will be there – and you should be, too.

Over the last 20 years, we have made huge strides in abstracting common complexities from the lives of developers. Wave after wave of innovation has driven the technology cycle. Enterprises have organized and executed around raising the delivery abstraction targeted by their developers. With each wave, we have simplified the effort, reduced the time to deliver and hastened the pace of innovation.

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.

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.

An examination of how wasifills—a component adapter pattern like polyfills, but for components—can help bridge the gap between today's rapidly changing standards landscape and the future of interoperable components facilitated with wit and wit worlds. It's an amazing time to be on the bleeding edge of the WebAssembly adoption curve, but it's not without risk.

At the Pasadena leg of Kubernetes Community Days (co-located with SCaLE 20x), I had the chance to talk to 100 or so Kubernetes enthusiasts, to give my perspective on WebAssembly, through the lens of a Kubernetes veteran.