Skip to main content

Engineering @ Cosmonic

Brooks Townsend
Brooks Townsend
Brooks Townsend
||7 min read

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.

Taylor Thomas
||11 min read

As core contributors of CNCF Sandbox Project wasmCloud, it's always exciting to see specific industries prove that Wasm can bring real-world benefits and efficiencies. In particular, we love seeing how Wasm can compliment existing technologies – our work with Adobe is a great example of how wasmCloud can enhance Kubernetes infrastructures. On the reverse side of the same coin, a new use case, developed within the operations and services (OSS/BSS) side of the telecoms industry, has revealed the potential of Wasm as a replacement for Kubernetes.

Dan Norris
Dan Norris
Dan Norris
,
Joonas Bergius
Joonas Bergius
Joonas Bergius
||5 min read

  • Seamlessly operate WebAssembly across any K8s distribution via GitOps pipeline
  • Orchestrate CNCF wasmCloud across K8s with Kubernetes Custom Resource Definition (CRD)
  • Wadm supercharges Cosmonic Connect Kubernetes to create new Kubernetes controller
Taylor Thomas
Taylor Thomas
Taylor Thomas
||9 min read

If you’ve been following anything in the Cloud Native space right now, chances are that you’ve heard of WebAssembly (Wasm). As someone who works at a Wasm company, it should come as no surprise that I think Wasm is the future of software development. But, let’s be honest, you probably aren’t going to just dismiss Kubernetes and go all-in on the first Wasm-related project you find.

At Cosmonic, we’ve always believed it important that Wasm and wasmCloud (the soon-to-be incubating CNCF project we contribute to and help maintain) are compatible with, but not dependent on any pre-existing technology. Guided by that principle, we have long provided integrations with Kubernetes, as most people operating in the cloud native ecosystem are running in or integrated with it. What has been interesting to see is how people are choosing to integrate with it. This post outlines a couple of ways to integrate Wasm with Kubernetes, and it gives a clue as to why we’ve designed our platform to integrate with Kubernetes the way it does. With that in mind, let’s dive in!

Bailey Hayes
Bailey Hayes
Bailey Hayes
||2 min read

WIT, or Wasm Interface Types, allows WebAssembly modules to communicate with each other using complex data types. WIT is a language agnostic interface definition language (IDL) that enables composing WebAssembly components, regardless of source language, using language-specific bindings. If you're using a WIT-generated set of language bindings it will feel just like using a regular language SDK. If you're writing your own WIT, then this guide is for you!

Brooks Townsend
Brooks Townsend
Brooks Townsend
||2 min read

New to the Cosmonic PaaS, we’re introducing an easy-to-use UI for managing declarative Wasm applications. Just like the platform’s opinionated views for Logic and Infrastructure, the new Application View provides a user interface for interacting with Wadm applications defined using the Open Application Model (OAM). This view includes an in-UI YAML editor and YAML validation.

Kevin Hoffman
Kevin Hoffman
Kevin Hoffman
||9 min read

Time is one of those things we all take for granted. Time marches on and does a dozen other things described by pithy sayings on T-shirts and motivational posters. When it comes to software, however, time is often our worst enemy. In this blog post, I talk about some patterns for dealing with the passage of time in event sourced applications.

Brooks Townsend
Brooks Townsend
Brooks Townsend
||2 min read

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.

Kevin Hoffman
Kevin Hoffman
Kevin Hoffman
||6 min read

Recently I had the opportunity to pick the brain of someone who has more experience and exposure to large scale, event-sourced systems than I do. We talked about event sourcing, specifically command processing, the subject of this blog post. It was an enlightening conversation that reminded me that insight is information tempered with experience. No amount of book reading is a substitute for learning from watching things go horribly wrong in production 😃.

Keep up to date

Subscribe to Cosmonic for occasional communication straight to your inbox.