SQLite in Wasm... why and how?
summary
Shows how the SQLite C engine compiled to WebAssembly provides four JavaScript-facing APIs (C-like, object-oriented, message-based webworker, and promise wrappers) to run full SQL in the browser. Demonstrations load the Chinook database and run joins, window functions and group-by queries in about 5–80 ms; persistence can use localStorage/sessionStorage (~5 MB) or the Origin Private File System (up to ~60% of disk) via webworkers for nonblocking, near-native performance, and user-defined functions require compiling into Wasm.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:21What is SQLite
- 1:47SQLite in Wasm benefits
- 2:50SQLite in Wasm history
- 3:33SQLite in Wasm API
- 4:56Web Workers and persistence
- 5:57Ideal use cases
- 7:03Live demo
- 9:55Browser APIs key
- 13:46Q&A
related talks
36mSQLite in Wasm: A Glimpse into the Future of Shared Libraries
32mWebAssembly functions for your SQLite-compatible database
09mFun with SQLite and Wasi-Libc
30mHow WebAssembly is changing the Web and what it means for Angular
29mBuild Database Driven Applications in Wasm
21mHit the Ground Running with WebAssembly
01h 00mBlazor, .NET 6, and WebAssembly
50mWebAssembly and the Future of the JVM Ecosystem
