Build Database Driven Applications in Wasm
summary
Three concrete approaches decide whether this is useful: host functions via frameworks like Spin framework that keep DB connections outside the VM, WASI‑like socket APIs that let existing clients run in Wasm, or embedding a VM as a UDF for in‑db logic. Examples show MySQL, TiDB, and Redis connectivity, Rust + Tokio/Mio tweaks for nonblocking WASI-like socket APIs, Docker Compose demos that run a Wasm microservice with MariaDB, and tiny artifacts (3 MB app server, 700–800 KB Redis/Postgres demos) that actually work.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:25Database Application
- 1:06Database for Microservices
- 2:14Database to WebAssembly
- 5:56Sample Application
- 8:19Architecture Diagram
- 9:40Demo
- 16:03Size comparison
- 16:55How it works
- 19:52Nodejs
- 20:59Socket Support
- 21:13Frameworks
- 21:38Dapper API
- 25:23Questions
- 26:51Examples
- 28:07Flows Network
related talks
13mLightning Talk: Revolutionizing Application Architecture with Wasm Powered Database Ex...
48mBuild and Manage Wasm Applications using Container Tools
39mUnleashing the Power of WASM: Revolutionizing Database Scalability and Application Architectures
56mServer-side Wasm Applications: Replacing Docker with WASI
07mBeyond The Browser: Wasm in Your Cloud Development Workflow
15mSQLite in Wasm... why and how?
36mSQLite in Wasm: A Glimpse into the Future of Shared Libraries
37mDevelop Wasm Applications with Docker