KvSQL DB on KvSQL.com

KvSQL Launches With an Embedded Engine and a Database Server on One Set of Records

Thu, 22 Oct 2026 00:00:00 +0000

KvSQL 0.1.0 is out. It’s a key-value store and an SQL database that keep one copy of the data between them. Read a row by its key and it comes straight from the storage tree, with nothing parsed or planned. Ask SQL about the same rows and it reads the same bytes. One transaction covers both, and an index stays right whichever way a row was written.

The release has two products. KvSQL Engine is a Rust library you put in your own program: one file on disk, no server, and no dependencies beyond the Rust standard library. KvSQL DB is built on it: kvsqld serves a database file over HTTP with JSON, and kvsql is a shell that talks to the server or opens a file directly.

How KvSQL Was Tested With Power Cuts, Killed Processes and 30000 Statements Checked Against SQLite

Thu, 22 Oct 2026 00:00:00 +0000

A database makes one promise above the rest. When it says a commit is done, the data is there, even if the power goes a moment later. And if the power goes during a commit, the file holds the whole transaction or none of it, never part. Most of KvSQL’s tests are aimed at that promise, from several sides.

All the figures below come from one recorded run of the project’s test script, scripts/record-results.sh, on a Linux container with two virtual CPUs, on October 22, 2026. The full output is in the repository under test/results/latest. CI runs the same script on Linux and macOS on every change.

Case Study: An Edge Gateway Collecting Sensor Readings Over HTTP With kvsqld

Thu, 22 Oct 2026 00:00:00 +0000

An edge gateway sits between a set of devices and the rest of the world. Sensors post readings to it, a dashboard on the same network shows the latest value per device, and someone asks about history: averages, peaks, the hour a fridge ran warm. The gateway is often a small box with no room for a database team, so it should be one program and one file.

This case study runs that set-up with kvsqld. Twenty simulated devices post readings over HTTP on their own connections, while a dashboard reads the latest value by key and asks SQL for history. It’s part of case_studies.rs in the repository. The figures are from its recorded run of October 22, 2026, on a real file on a Linux container with two virtual CPUs. The output is in case-studies.md.

Use Example: Working With a Database File in the kvsql Shell

Thu, 22 Oct 2026 00:00:00 +0000

Sometimes you just want to look inside a database. Maybe a test left a file behind, or you’re checking what a service wrote, or you want to try a query before putting it in code. The kvsql shell opens a file directly, with no server running, and takes SQL and key-value commands side by side.

kvsql --file jobs.kvsql

Here is a short session, as the project’s use example program ran it through the shell’s own command code, one command at a time the way -c takes them. The output is exactly what came back: