Filesystem IO for Rust storage engines: journal substrate, io_uring, NVMe passthrough, atomic writes, cross-platform durability.
-
Updated
May 18, 2026 - Rust
Filesystem IO for Rust storage engines: journal substrate, io_uring, NVMe passthrough, atomic writes, cross-platform durability.
Generic durable segmented store with write-ahead log and compaction
A crash-safe, deterministic WAL storage engine built on io_uring
A storage engine where forking a database costs nothing. Immutable content-addressed pages, O(1) fork/snapshot/rewind, crash-safe by construction. The shared foundation under FlockDB and LoomDB.
Persistent, networked key-value store built from scratch in Rust: append-only storage, crash recovery, background compaction, and a sharded concurrent index served over a custom TCP protocol.
Write-ahead log primitive for Rust storage engines - durable, recoverable, lock-free.
IronBus: a simple, resilient, hyperscale, edge-first, cross-platform single-topic message queue in Rust.
rust crate for durability evading crash and powercut dataloss
DBlicious keeps PostgreSQL and MySQL semantics in their upstream engines while sharing durability, object storage, timelines, and lifecycle machinery.
Semantic application storage for Rust with typed storage spaces, provider capabilities, transactions, durability policies, and portable backends.
KV Store to store data in a collection of key-value pairs.
A durable, high-throughput write buffer for Rust - microsecond fsync'd acks over a Unix socket, N→1 batched commits to your database, and crash-safe WAB replay.
Row-format write-ahead log primitive for Rust databases. Group commit, fsync coordination, sharded writers, crash recovery, replay. Backend-agnostic durability layer for traditional row-oriented storage engines. Conventional ARIES-style semantics, no novel tech.
To associate your repository with the durability topic, visit your repo's landing page and select "manage topics."