https://lavik.dev/en/blog/Lavik architecture, benchmarks, and release news.enhttps://lavik.dev/en/blog/lavik-field-notes-2026-09-26/https://lavik.dev/en/blog/lavik-field-notes-2026-09-26/A worked capacity model shows why moving values to NVMe changes the budget without removing index memory, reclamation headroom, or shared server costs.https://lavik.dev/en/blog/lavik-spdk-performance-and-capacity/https://lavik.dev/en/blog/lavik-spdk-performance-and-capacity/Understand the September 18 benchmark, verify basic commands, and model capacity savings without mistaking them for deployment-wide savings.https://lavik.dev/en/blog/failover-intent-authority-and-evidence/https://lavik.dev/en/blog/failover-intent-authority-and-evidence/Lavik’s control-plane decisions distinguish a planned handoff from owner loss. Follow the state transitions that prevent stale preparation and observations from becoming authority.https://lavik.dev/en/blog/fast-restart-with-index-checkpoints/https://lavik.dev/en/blog/fast-restart-with-index-checkpoints/Lavik treats a shutdown checkpoint as a one-use recovery accelerator. Its publication, consumption, and fallback rules are the substance of the design.https://lavik.dev/en/blog/grouped-collections-on-ssd/https://lavik.dev/en/blog/grouped-collections-on-ssd/Large hashes, lists, sets, and sorted sets need more than a place to store one giant value. Lavik uses collection-specific routing and atomic graph publication.https://lavik.dev/en/blog/inside-lavik-request-path/https://lavik.dev/en/blog/inside-lavik-request-path/An SSD-backed Redis interface needs more than asynchronous reads. Follow a request through connection state, admission, partition ownership, and reply backpressure.https://lavik.dev/en/blog/lua-functions-as-a-durable-catalog/https://lavik.dev/en/blog/lua-functions-as-a-durable-catalog/A function library must become consistent across workers, survive restart, and travel through replication. Lavik stages complete catalogs before making them visible.https://lavik.dev/en/blog/multi-key-transactions-across-partitions/https://lavik.dev/en/blog/multi-key-transactions-across-partitions/Key ownership makes local work efficient. Multi-key commands need a separate design for scheduling, lock lifetime, command errors, and durable completion.https://lavik.dev/en/blog/replication-acks-and-recovery-boundaries/https://lavik.dev/en/blog/replication-acks-and-recovery-boundaries/Lavik tracks native replication by history and logical flow. Understand what an acknowledgement proves, what a restart discards, and why failover needs additional evidence.https://lavik.dev/en/blog/why-lavik-separates-index-from-values/https://lavik.dev/en/blog/why-lavik-separates-index-from-values/Follow the ownership, append, read, and reclamation decisions behind a value store that can grow beyond DRAM capacity.https://lavik.dev/en/blog/reading-the-benchmark/https://lavik.dev/en/blog/reading-the-benchmark/Read the measured results, their conditions, and the questions they leave open.https://lavik.dev/en/releases/0-1-0-beta-1/https://lavik.dev/en/releases/0-1-0-beta-1/A pinned reference for evaluating the first 0.1.0 beta.