Wasm Workers Server

Wasm Workers Server (WWS) is a reasonably maintained alternative, though there are nuances to consider:

# Maintenance Status & Community Activity * **Open-source** under Apache 2.0 by VMware (now VMware Labs). ([wasmlabs.dev][1]) * Actively developed until late 2023–2024, with WWS v1.7.0 released in October 2023.  * Notably, the GitHub repo is **marked for archival soon**, with plans to continue development through a community-maintained fork at `webassemblylabs/wasm-workers-server` - github

# Is There a Store or Community Module Repository? * WWS supports **polyglot “workers”**—Rust, JS, Go, Python, Ruby, Zig, etc.—with examples hosted in the repo under `examples/` and documented guides.  * **No official central “store”** for third-party modules or a package registry, but the GitHub project contains examples and community contributions. 

# Community Engagement & Longevity * \~534 stars and \~41 forks—shows solid interest. ([github.com][2]) * Issues remain active through mid-2024, including feature requests like dynamic loading, HTTP internals improvements, and runtime updates.  * The archiving means **community governance** is likely to continue via the new fork—so you’d want to target that for any long-term dependency.

# Summary & Guidance * WWS is **well-built and feature-rich**, with strong multi-language WASM support via Wasmtime. * Its architecture includes **file-based routing**, built-in memory store, and polyglot WASM running. * However, it **lacks an ecosystem store**—you’ll either use the included examples or build/share your own modules. * Its future depends on the **community fork** under `webassemblylabs`; keep an eye on that if you choose to build on it.

# Considerations * **Pro**: You can quickly assemble federated wiki-style endpoints using WWS by writing custom workers. * **Con**: No native support for JSON querying (JQL/Rhai) or federated wiki features—those would need to be built as polymorphic WASM modules. * **Con**: As the original repo is archiving, your comfort level with maintaining or engaging with the new community fork matters.

# What is Wasm Workers Server (WWS)? A self-contained, serverless framework by VMware (archive). It automatically detects and runs WebAssembly—or other supported runtimes like JavaScript, Python, Ruby, and Go—in response to HTTP requests. Each file becomes an endpoint, and the server handles routing and sandboxing via Wasmtime

# Key Features * **Filesystem-based routing**: Place files like `hello.js` or `index.wasm` in folders—no manual routing. ([wasmlabs.dev][2]) * **Polyglot support**: Write handlers in Rust, JS, Go—even Python—compiled to WASM or interpreted inside Wasmtime. ([workers.wasmlabs.dev][1]) * **Lightweight & portable**: Runs on your laptop, server, Raspberry Pi, or Docker. ([classcentral.com][3]) * **Built-in KV store** and CORS features. ([workers.wasmlabs.dev][1])

# Comparison with Your WarpDrive Vision | Feature | Wasm Workers Server (WWS) | WarpDrive | | ---------------------------------- | ---------------------------------------------------- | -------------------------------------------------------------- | | **Endpoint architecture** | File-based, one handler per WASM/module per endpoint | Flexible routing with handlers for JSON fetch, JQL, WASM, etc. | | **Polyglot WASM support** | Yes—Rust, JS, Go, Python, Ruby, Zig | Yes, via live code, Rust, etc. modular components | | **JSON processing** | General execution, but no built-in JSON query system | Built-in JQL/Rhai-powered JSON transformation | | **Federated wiki awareness** | Generic HTTP/WASM framework, no wiki-specific logic | Tailored to federated wiki JSON, drag-drop flags, guides | | **Integration with Tauri/desktop** | Primarily server-side | Designed to share WASM across both server and Tauri app |

# Too Similar? WWS is a powerful general-purpose WASM server, but it doesn't include: * JSON processing pipelines with JQL/Rhai * Federated wiki JSON support or interactive drag‑drop context * Tight integration with desktop apps like Tauri for guide rendering

The **WarpDrive + Tauri Guide** ecosystem packages these concerns and binds them to your niche workflow, which isn’t available in WWS.

# Summary Wasm Workers Server is excellent for **serverless WASM routing**, but your vision goes beyond that. It incorporates: * Rich data-processing logic for federated wiki content * Unified deployment across both local HTTPS server and desktop GUI * WASM modules that serve content *and* presentation in multiple environments --- ### ✅ Conclusion You *can* borrow architectural patterns from WWS—especially auto-service loading and multi-language runtime support—but **WarpDrive** still brings unique capabilities specific to federated wiki workflows and desktop guide rendering. It’s quite original and valuable to build from scratch.

# Referenses 1. Wasm Workers Server - wasmlabs.dev 1. Wasm Workers Server - workers.wasmlabs.dev 1. Wasm Workers Server - wasmlabs.dev 1. Portable Serverless Apps - classcentral.com