- Brings WASI 0.2 and components to production environments
- Meet wRPC: a protocol for composing components over distributed networks
wash build
components in Python, JavaScript, .NET, C++, and more
Engineering @ Cosmonic
WASI 0.2.0 and Why It Matters
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.
Bringing WebAssembly to Telecoms with CNCF wasmCloud
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.
WebAssembly on Kubernetes with Argo CD and Cosmonic
- 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
Do you need runwasi to run WASI?
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!
Get WITtier with this handy guide to Wasm Interface Types
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!
Documentation-First Event Sourcing with Concordance, wasmCloud, and Event Catalog
Making sure that the team has a holistic view of the event flows throughout an application while still being able to synchronize code, schemas, and documentation is probably harder than actually writing the code.
Application View: Cosmonic Introduces Declarative Wasm Application Management
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.
Passing Time in Event Sourced Applications
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.
Personalizing your Wormhole Experience
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.
Keep up to date
Subscribe to Cosmonic for occasional communication straight to your inbox.