7 posts tagged with "components"

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.

• A few major themes came through during the event. By far, the WebAssembly Component Model dominated conversations with many looking to understand how it works and how close components are to stabilization. Language interoperability was also front of mind, and there was lots of fresh innovation on show: from Siemens' use of Wasm in embedded systems to fresh demos showing componentize-py in action.

• Component Model update published: WASI-Preview 2 now MVP
• Cosmonic componentizes wasmCloud and Cosmonic PaaS
• Creates standards-based, vendor-neutral environment for building distributed apps
• Spurs wave of PaaS innovation

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.

Some thoughts and reflection on my first day using Wasm components for something more involved than hello world.

An examination of how wasifills—a component adapter pattern like polyfills, but for components—can help bridge the gap between today's rapidly changing standards landscape and the future of interoperable components facilitated with wit and wit worlds. It's an amazing time to be on the bleeding edge of the WebAssembly adoption curve, but it's not without risk.