SQLite on the Factory Floor: Local-First Telemetry When the WAN Goes Dark

Three winters ago, a forty-spindle aerospace machining shop outside Linkoping lost three shifts of turbine-bracket production without a single broken cutter or power dip. An excavator four kilometres down the valley sliced their fibre conduit, and the shop's browser-based manufacturing execution system refused to release G-code revisions or record torque-wrench sign-offs while its remote API gateway was unreachable.

Within six months, the plant's two-person tooling team replaced the SaaS terminal at each workcell with a fanless DIN-rail Linux box storing active job travellers, calibration certificates, and spindle vibration samples inside a single SQLite database running in Write-Ahead Logging (WAL) mode.

Sub-Millisecond Reads Right Beside the Spindle

Eliminating network round-trips transformed operator responsiveness. Barcode scans against 420,000 historical tool-offset records resolve in 0.3 milliseconds off industrial NVMe flash. Concurrent readers never block the single telemetry writer appending 100-hertz spindle load frames, and hourly incremental snapshots replicate over WireGuard to the central warehouse whenever external connectivity is healthy.

PRAGMA journal_mode = WAL;
PRAGMA synchronous = NORMAL;
PRAGMA foreign_keys = ON;
PRAGMA busy_timeout = 5000;

Single-File Archival Clarity

Aviation regulators require component traceability archives to remain readable for thirty years. A self-contained SQLite file—documented down to its byte-level page format in the public domain—shares the archival durability of the printed service binders praised in Why Technical Manuals Stopped Working—and What 1960s Oscilloscope Books Got Right and the bounded failure modes of Deterministic State: How Nordic Rail Interlockings Prove Two Trains Cannot Meet. Long after today's cloud APIs deprecate their endpoints, a single .sqlite file on cold storage will open cleanly with zero external servers.