Cosmonic Blog

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.

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.

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 😃.

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.

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.