wasm-edge-computing-expert

WASM & Edge Computing Expert

English | Bahasa Indonesia

---

English

Orchestration & Integration

• Upstream Languages & Toolchains: rust-programming-expert, go-programming-expert, bun-runtime-expert
• Edge Deployment Targets: cloudflare-workers-expert, cloud-hosting-expert, api-gateway-proxy-expert
• Sandbox & Execution: ephemeral-wasm-sandbox-executor, local-slm-edge-ai-expert
• Client Performance: performance-web-vitals, web-3d-graphics-expert, anti-slop
• Lifecycle & Governance: zero-to-prod-orchestrator, session-memory-manager

Description

A specialized guide for writing, compiling, and deploying WebAssembly (WASM) modules both on the Edge and in the browser. Covers the new WebAssembly System Interface (WASI) Preview 2, serverless execution environments (Spin, Cloudflare Workers, Fastly Compute), and bidirectional JavaScript-to-WASM interop.

Trigger Conditions

• When porting heavy computational tasks (image processing, video encoding, cryptography) from JavaScript to Rust/Go via WASM.
• When deploying ultra-fast, cold-start-free serverless functions on Cloudflare Workers or Fermyon Spin.
• When the user asks about "WASI", "WebAssembly", or "Edge computing performance".
• When bridging legacy C/C++ libraries to run in the browser using Emscripten.

Core Architectural Guidelines

1. Language Choice & Toolchain

• Rust (Recommended): Use wasm-pack for browser modules and cargo component for WASI Preview 2. Rust offers the smallest binary sizes and no garbage collector overhead.
• Go: Go 1.21+ has native WASI support (GOOS=wasip1 GOARCH=wasm), but binaries are larger due to the included runtime. Use TinyGo for smaller binaries.
• AssemblyScript: Use when the team only knows TypeScript, though performance is slightly less than Rust.

2. Browser Integration (wasm-bindgen)

When writing Rust for the browser, minimize crossings between JS and WASM, as serialization is expensive.

use wasm_bindgen::prelude::*;

#[wasm_bindgen]
pub fn compute_heavy_task(input: &[u8]) -> Vec<u8> {
    // Process data entirely in WASM before returning
    input.iter().map(|&b| b.wrapping_add(1)).collect()
}