A durable history.
The write-ahead log records operations for recovery. Synchronisation establishes their durability.
An independent storage engine
ORDER FROM EVERY WRITE.
A Rust-native LSM database engine. Built around the journey from incoming operations to ordered, persistent data.
The write-ahead log records operations for recovery. Synchronisation establishes their durability.
Memtables collect updates before flushing them into immutable, sorted files.
Sorted runs organise keys on disk. Indexes and filters help narrow the search for a value.
Compaction combines runs and reclaims obsolete versions when they are no longer needed.
Built in the open. Still taking shape. These are the principles behind the engine, not a checklist of completed features.
Follow the implementation ↗On the shelf / The journal
Long-form engineering notes. Real design decisions. A working record of how a storage engine is built.
Coordinating Batch Commits for Concurrent Durable Storage
Read articleGrouping write operations in Ordinum and using Rust's type system to represent batch states
Read articleHow Ordinum implemented thread local storage for it's subsystems and the design decisions involved.
Read articleInside the product
Ordinum explores the machinery behind a log-structured merge-tree storage engine. The journal documents that work as it develops; the source is the place to inspect the implementation.
Explore the source ↗Batches, sequencing and commit coordination connect the caller to the WAL and memtable.
Read about writes →Rust types, allocation lifetimes and thread-local storage shape how the engine manages its work.
Read about threads →These are evolving engineering journals, not a claim of production readiness or a finished reference manual.
Meet the author →