← Tuesday, October 20, 2026DatabasesTool

KiviDB shards a Redis-compatible in-memory keyspace across threads

github.com 12 min read Editor score 6/10

KiviDB supports RESP2 and RESP3, shards its keyspace across threads, and uses io_uring on Linux with a Tokio fallback elsewhere. Those implementation choices are relevant to engineers evaluating in-memory data stores, though the excerpt gives no benchmark results.

What
KiviDB is a Rust-based, Redis-compatible in-memory database with built-in full-text and vector search.
How
Its sharded key-value design uses every core and persists to snapshots plus an optional append-only file.
Why it matters
RESP2 and RESP3 compatibility lets existing Redis clients and libraries work unchanged, while built-in search supports additional workloads.
commands persists optional pers… Redis protocol in-memorykey-value design snapshots append-only file
KiviDB accepts Redis-protocol commands, operates on an in-memory key-value design, and persists data. Sketched from the article's own text.

Discussion

Discussion is not switched on yet. Use Note above to keep your own thoughts on this story.

Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.

Your note

Private to you. Stored in this browser, and synced to your account when you are signed in.