Storine v0.3.0

Releases

Changelog

Versions follow Semantic Versioning. Before 1.0, a minor version (0.x) may change on-disk or wire formats; docs/COMPATIBILITY.md says what each kind of release may change and how to upgrade.

0.3.0 (2026-11-17)#

Bulk imports that don't pause, and shorter stalls with many writers. Telling the store how many records are coming, from the embedded API, any client library, SQL or one server setting, on a single server or any cluster, cut the slowest 0.01% of writes during a load from 1.1 ms to 23–30 µs. The worst stall with four writers on four CPUs fell from 6.5–8.1 ms to 4.3–4.6 ms (docs/BENCHMARK_REPORT.md section 8.11).

This is a minor release because the Rust API gained a field: EngineConfig literals that list every field without ..Default::default() must add expected_records. Nothing else is incompatible.

Upgrading from 0.2.x: replace the binaries (install.sh / install.ps1 again) and restart. The on-disk formats are unchanged and both protocols only gained requests, so, unlike a usual minor release, a cluster can be upgraded one node at a time and 0.2.x and 0.3.0 nodes can run together. While they do, reserve sizes only 0.3 nodes (a range node skips peers that refuse its share), and a 0.2 server answers reserve with Invalid. Embedders: add expected_records to EngineConfig literals that need it.

Formats and protocols#

Release checks#

CI on Linux x86_64 and arm64, macOS arm64 and x86_64, and Windows: the test suite, lints, binary sizes and the install scripts. Process chaos, 40 runs on x86_64 and on arm64. The power-loss suite (a crash at every I/O call) also runs with expected_records set. Benchmarks against 0.2.1, LMDB and RocksDB (section 8.11). reserve was checked from each of the eight client libraries against a running server, through SQL, and on a three-node range cluster (every node sized); STORAGE_EXPECTED_DOCUMENTS by starting the server with it. Not repeated: the soaks, full SDK suites and sanitizers, since replication and the unsafe code are unchanged since 0.2.0, and the clients and nodes only gained reserve.

Added#

Fixed#

Known limitations#

0.2.1 (2026-11-16)#

A patch release: clearer command-line messages, and the documentation website. The engine, the protocols and the on-disk formats are those of 0.2.0.

Upgrading from 0.2.0: replace the binaries (install.sh / install.ps1 again) and restart. A cluster can be upgraded one node at a time, and 0.2.0 and 0.2.1 nodes can run together.

Formats and protocols#

Release checks#

CI on Linux x86_64 and arm64, macOS arm64 and x86_64, and Windows: the test suite, lints, binary sizes and the install scripts. The release workflow installs the published binaries with the install scripts on each platform and checks their version. The checklist's chaos runs, soaks, SDK suites and sanitizers were not repeated: no code they cover changed since 0.2.0.

Added#

Fixed#

0.2.0 (2026-11-16)#

Three features that existed only in the embedded engine are now in the server: encryption at rest, point-in-time recovery and multi-region placement (docs/TECHNICAL.md sections 7, 8 and 13). Single-group cluster writes are 5–8× faster, checkpoints end under any write load, the web console was redesigned, and install scripts set Storine up in one line.

Upgrading from 0.1.x: back up, stop every node, start 0.2.0 on the same data directories (docs/COMPATIBILITY.md). Data written by 0.1.1 is read as it is: tested for a single server (stopped cleanly and killed), a 3-node cluster and a 3-node range cluster. Mixed-version clusters are not supported, and 0.1.x cannot open data that 0.2.0 has written.

Formats and protocols#

Release checks#

Run on the release candidate (docs/RELEASE.md); the fixes they led to are listed under Fixed.

Added#

Measured#

Fixed#

Changed#

0.1.1 (2026-11-13)#

Binaries for Linux, macOS and Windows, and a web console. On-disk formats, the client protocol and the node-to-node protocol are unchanged from 0.1.0: a rolling upgrade works, and 0.1.0 and 0.1.1 nodes can run in one cluster.

Added#

Changed#

Fixed#

Documentation#

0.1.0 (2026-11-13)#

The first release. Everything below is new.

Engine#

Server and clusters#

Clients#

Performance#

Measured on AWS c7i.xlarge against LMDB and RocksDB at equal durability (docs/BENCHMARK_REPORT.md section 8):

Fixed before release#

Known limitations#

Edit this page on GitHub