JS/WASM calls

Problem

What becomes confusing, fragile, or impossible without understanding JS/WASM calls? This lesson answers that through explanation, a worked example, two runnable exercises, and a reference solution. No teacher-supplied worksheet is required.

WebAssembly brought a portable low-level compilation target to the browser; SQLite brought a mature relational engine into one embedded file.

Concept explanation

JS/WASM calls belongs to “WebAssembly as a boundary”. JS/WASM calls is inspected by introducing one realistic failure and proving root cause before repair.

For JS/WASM calls, trace concrete input, state transition, output, and failure through an explicit low-level or relational boundary where memory, crossings, schemas, queries, and persistence costs can be measured.

JavaScript calls into a WASM module whose linear memory and host imports form an explicit boundary. SQLite executes queries over pages, indexes, and a planner. Apply that model to supplied normal, boundary, and failure cases; each case below names its input and expected evidence.

Example bank

Compare normal, boundary, failure, and cross-layer cases. Predict each observation before revealing the explanation.

Worked example

Start from supplied lab.sql. Focus: Capture healthy JS/WASM calls baseline from: Call tiny exported arithmetic function and inspect module exports/memory.

1. Run: sqlite3 :memory: < lab.sql
2. Save baseline evidence. Inspect module exports, memory, JS/WASM crossings, schemas, indexes, transactions, query plans, OPFS files, and recovery.
3. Boundary case: Record JS/WASM calls behavior at: Compare one million calls versus one batched call.
4. Failure case: Diagnose this exact JS/WASM calls failure before editing: Read beyond agreed memory region and validate bounds in host wrapper.

RESULT
Evidence identifies first divergence, repair changes only proven cause, and rerun restores: Benchmark separates startup, crossing, and compute; batch reduces crossing overhead. Starter-level baseline: Query plan reports use of observations_topic; final query prints baseline.

Starter material

Create lab.sql, paste this exact content, then run the command below.

CREATE TABLE observations (id INTEGER PRIMARY KEY, topic TEXT NOT NULL, result TEXT NOT NULL);
INSERT INTO observations(topic, result) VALUES ("JS/WASM calls", 'baseline');
CREATE INDEX observations_topic ON observations(topic);
EXPLAIN QUERY PLAN SELECT result FROM observations WHERE topic = "JS/WASM calls";
SELECT result FROM observations WHERE topic = "JS/WASM calls";

STOP / CLEANUPIn-memory SQLite exits after script. Stop any local web server with Ctrl+C.

Independent exercise

Prove root cause: JS/WASM calls

1. Create second case from blank file: Record JS/WASM calls behavior at: Compare one million calls versus one batched call.
2. Then create controlled failure: Diagnose this exact JS/WASM calls failure before editing: Read beyond agreed memory region and validate bounds in host wrapper.
3. Use WASM debugger · SQLite CLI · EXPLAIN QUERY PLAN · OPFS to prove behavior, then repair controlled failure.
4. Compare result against supplied acceptance checks and reference approach before marking complete.

Expected result

• Evidence identifies first divergence, repair changes only proven cause, and rerun restores: Benchmark separates startup, crossing, and compute; batch reduces crossing overhead.
• Query plan reports use of observations_topic; final query prints baseline.
• Controlled JS/WASM calls failure produces captured evidence; repair restores stated invariant without hiding error.

Hints

Solution

Attempt both exercises before opening reference approach.