Sandboxing the code AI agents run, and the systems that make it dense and fast. Engineering deep dives and security notes from the Cosmonic team.
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!
After a week spent in the company of WebAssembly (Wasm) experts and enthusiasts, we've come away from the Linux Foundation's inaugural WasmCon with one conclusion - WebAssembly is capturing developer imagination in all sorts of industries. As the Bytecode Alliance and W3C Wasm Working Group release the latest stable iteration of Wasm standards - WASI-preview 2.
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.
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.
In a little over a week, two exciting new events in the WebAssembly (Wasm) calendar will kick off in Seattle. We’re looking forward to seeing everyone at the The Linux Foundation's inaugural WasmCon, and the Bytecode Alliance’s Componentize the World Hackathon. Both events are being held close to one another – WasmCon in Bellevue, WA on September 6 - 7, and the ‘Componentize the World’ hackathon on Friday September 8th in Redmond, WA.
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.
From the early days of Cosmonic, Kevin and I embarked on this venture with a shared dream and an unwavering passion for innovation. As we've navigated the fast-paced and dynamic world of startups, we've continuously evaluated the best ways to harness the strengths of our team and achieve our collective vision. I’m excited to share some organizational news that I'm writing to share exciting news about some organizational shifts that Kevin and I believe will propel Cosmonic forward with even greater momentum.
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.
