7 posts tagged with "WebAssembly"

• 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

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.

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!

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.

From the beginning of our days developing wasmCloud, we took a stance to be compatible with today's technology without being dependent on it. So, wasmCloud needed to be able to:

• Run inside or outside of a container
• Run inside of Kubernetes or another orchestrator and run without it
• Run on Linux, but also support Mac and Windows (and not just WSL)
• Etc

One of the things we've run into as we've worked with customers and developed our own examples at Cosmonic is the need to serve UIs that are consuming services you are running inside of wasmCloud. Our own examples required you to either run the UI using npm or to run a docker image. This felt less than ideal and didn't fit with our vision of WebAssembly being the future of distributed computing.

We just released a new version of the petclinic example that demonstrates how you can bundle up a UI for your application into a single actor. Now when you start the full petclinic example, the API and UI are served from the same place

Hybrid meetup hosted by Stuart Harris, co-founder, Red Badger on Wed., March 2, part of a series called “Wheel of Tech”

Guest presenters from Cosmonic included Brooks Townsend, lead software engineer, and Taylor Thomas, engineering director. Also presenting was Kostya Babanakov, enterprise solutions engineer, SingleStore UK and EMEA.

This event focused on why the use of WebAssembly server-side represents a major revolution in platform design as we move beyond the cloud as a destination. Coupled with products like wasmCloud and NATS, WebAssembly is creating a whole new paradigm for cloud native and eliminating entire classes of problems in the process.