Build a tiny cross-boundary function

Problem

What becomes confusing, fragile, or impossible without understanding build a tiny cross-boundary function? 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

Build a tiny cross-boundary function belongs to “WebAssembly as a boundary”. build a tiny cross-boundary function ships as one thin, inspectable slice of a JS/WASM boundary benchmark.

For build a tiny cross-boundary function, 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: Add build a tiny cross-boundary function to a JS/WASM boundary benchmark; demo it with: 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: Document and test shipped slice under: Compare one million calls versus one batched call.
4. Failure case: Add recovery behavior and a regression check for: Read beyond agreed memory region and validate bounds in host wrapper.

RESULT
Fresh clone or blank directory can run documented slice and reproduce: 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 ("build a tiny cross-boundary function", 'baseline');
CREATE INDEX observations_topic ON observations(topic);
EXPLAIN QUERY PLAN SELECT result FROM observations WHERE topic = "build a tiny cross-boundary function";
SELECT result FROM observations WHERE topic = "build a tiny cross-boundary function";

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

Independent exercise

Make it recoverable: build a tiny cross-boundary function

1. Create second case from blank file: Document and test shipped slice under: Compare one million calls versus one batched call.
2. Then create controlled failure: Add recovery behavior and a regression check for: 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

• Fresh clone or blank directory can run documented slice and reproduce: Benchmark separates startup, crossing, and compute; batch reduces crossing overhead.
• Query plan reports use of observations_topic; final query prints baseline.
• Controlled build a tiny cross-boundary function failure produces captured evidence; repair restores stated invariant without hiding error.

Hints

Solution

Attempt both exercises before opening reference approach.