InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now. Learn more →
Component-model Alternatives
Similar projects and alternatives to component-model
-
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
-
-
extism
The framework for building with WebAssembly (wasm). Easily & securely load wasm modules, move data, call functions, and build extensible apps.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
spin
Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
-
-
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better component-model alternative or higher similarity.
component-model discussion
component-model reviews and mentions
Posts with mentions or reviews of component-model.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-04-09.
-
Show HN: Obelisk – a WASM-based deterministic workflow engine
The structured concurrency paradigm in workflows is stricter to what I'm reading here [1]. The whole execution model is different from the Task [2], as workflows are transparently unloaded and replayed.
Obelisk has a concept called join sets, where child executions are submitted and awaited. In the future I plan on adding cancellation and allow custom cleanup functions.
[1] https://github.com/WebAssembly/component-model/blob/main/des...
[2] https://github.com/WebAssembly/component-model/blob/main/des...
-
Looking Ahead to WASIp3
Although WASIp3 has not yet been released, and the implementations are not yet ready for production use, now is a great time to experiment with it and provide feedback by opening issues on either the spec repo or the wasip3-prototyping repo. Whether you’re developing Wasm components or custom host embeddings to run components, we’d love to have your input. And if you’re a language implementer looking to add concurrency support for Wasm targets, we’d appreciate your input as well.
- Rust Is Eating JavaScript
-
Extensible WASM Applications with Go
I am kind of worried that the eagerness for more WASM features may irremediably harm the young ecosystem. Most of what Go added to WASM could be done natively if the component model proposal [1] was merged already.
The standard evolves slowly and as adoption rises we risk having to support more and more non-standard features forever, like WASI and now this.
[1] https://github.com/WebAssembly/component-model
- WASM-Native Orchestration
-
WASM Will Replace Containers
Fully agree with your point here, but wanted to point out that including C dependencies is actually one of the biggest reasons why Python support is hard for WebAssembly too.
Bolstering your point -- smart-and-hardworking people are working on this, which results in:
https://github.com/bytecodealliance/componentize-py/
which inspired
https://github.com/WebAssembly/component-model/blob/main/des...
which is made concrete by
https://github.com/dicej/wasi-wheels
-
Lua Is So Underrated
The WebAssembly component model is aimed at having composable components that can call each other. The components can be written in any language, compiled to WebAssembly, and interoperate: https://github.com/WebAssembly/component-model/
Extism is a plugin framework for WebAssembly:
https://extism.org/
https://github.com/extism/extism
Visual Studio Code can run WebAssembly extensions: https://code.visualstudio.com/blogs/2024/05/08/wasm
A project to bring WebAssembly plugins to Godot: https://github.com/ashtonmeuser/godot-wasm
WasmEdge can be embedded in applications: https://wasmedge.org/docs/embed/overview
Wasmer can be embedded in applications: https://blog.wasmer.io/executing-webassembly-in-your-rust-ap...
Wasmtime can be embedded in applications: https://docs.wasmtime.dev/lang.html
-
Ask HN: What are some unpopular opinions you got?
Eventually by using the component model which will expose the DOM API. It will get to direct wasm to WebIDL calls one day:
https://github.com/WebAssembly/component-model
The component model is being used for the WebAssembly System Interface (WASI):
https://github.com/WebAssembly/WASI/tree/main
In the meantime you can use JavaScript glue code auto-generated by your toolchain to access the DOM. This will be made better with builtins like the js-string-builtins proposal:
https://github.com/WebAssembly/js-string-builtins/blob/main/...
You can call JavaScript functions and DOM methods from wasm like this example from Hoot, which is a Scheme to wasm compiler:
https://spritely.institute/news/building-interactive-web-pag...
-
Introducing Spin 3.0
Let’s start with writing the interface for our image manipulation component. We’ll define our image manipulation package (using the WIT format) which contains one interface with two image transformations (grayscale and sepia):
-
Spin 3.0 – open-source tooling for building and running WASM apps
For the audience that would be looking to use the WASM Component Model, and not be an infrastructure implementer of it, whether or not they meet some definition of a method, the component model does define things called resources [1] that have "methods". You'll hold a "handle" to it like you would in your own programming language with the expected drop and/or GC semantics (once implemented [2]) because code is generated to access it like any other FFI like C/C++.
With that in mind, the other confusing thing one may come across is composition vs linking within your WASM runtime that supports the Component Model. When you hear "composition" think of compile-time merging of libraries such that the bundle may have less unresolved dependencies of WASM code/implemented component interfaces. Anything unresolved needs to be linked at runtime with your WASM runtime of choice, like wasmtime [3]. Pretty interesting reading/potential after reading if you ask me -- sounds like you could implement something like a custom Java classloader hierarchy.
But I'd agree with a statement saying it is still a long way for general usage.
[1] https://github.com/WebAssembly/component-model/blob/5a34794d...
[2] https://github.com/WebAssembly/gc
[3] https://github.com/bytecodealliance/wasmtime/blob/ba8131c6bf...
[4] https://www.digitalocean.com/community/tutorials/java-classl...
-
A note from our sponsor - InfluxDB
www.influxdata.com | 19 May 2025
Stats
Basic component-model repo stats
44
1,072
9.4
3 days ago
WebAssembly/component-model is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of component-model is Python.
Popular Comparisons
Sponsored
InfluxDB – Built for High-Performance Time Series Workloads
InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
www.influxdata.com