AltSql DB Live Demo

Twelve devices run AltSql Core, each on its own flash chip, and every ten seconds each saves a reading and sends the gateway what it has not confirmed yet. The gateway keeps every device in one AltSql DB file, the devices’ bytes unchanged, and answers two ways: SQL, and a direct path with no SQL step at all.

Simulated devices and file, real code. AltSql Core and AltSql DB run in this page, compiled to WebAssembly. The chips and the gateway’s file are emulated in memory, so the power can be cut at any write.

How to Run It

1. Ten minutes of the fleet. Sixty readings from each device arrive batch by batch, one transaction for each batch.
2. Ask with SQL. The last ten minutes of every device, and the plan the gateway chose: a range for each device, so it reads only those readings.
3. The direct path beside SQL. A device’s newest reading read both ways, and the stored bytes beside the device’s own.
4. Cut the power in a commit. While the gateway writes its pages, or its commit header. The file opens again, both headers are checked, and each device resends from the position the gateway holds.

On a wide screen the demo has more room: open it full screen.

About AltSql DB

AltSql DB is the gateway database of the AltSql family. Devices keep running AltSql Core, and a gateway that serves a whole fleet keeps their records in one AltSql DB file. In the browser the direct path read a device’s newest reading in about 1.4 µs, and SQL in about 150 µs, because the demo’s query still reads the device’s whole range and sorts it. About AltSql DB