HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
whispem
minikv
Rust2026–2026
whispem / minikv

minikv

Distributed, multi-tenant key-value and object store in Rust, with Raft consensus, WAL durability, and production-oriented operations.

7Distinct people
10Mentions
0Explicit recommenders
407GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Distributed, multi-tenant key-value and object store in Rust, with Raft consensus, WAL durability, and production-oriented operations.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day10 dated mentions

Observed mentions: 2026-01-17 19:39:36 UTC to 2026-02-03 14:19:59 UTC.

012342026-01-17 00:00:00 UTC to 2026-01-18 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 commentsJan 172026-01-18 00:00:00 UTC to 2026-01-19 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-19 00:00:00 UTC to 2026-01-20 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-20 00:00:00 UTC to 2026-01-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-21 00:00:00 UTC to 2026-01-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-22 00:00:00 UTC to 2026-01-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-23 00:00:00 UTC to 2026-01-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-24 00:00:00 UTC to 2026-01-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-25 00:00:00 UTC to 2026-01-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 252026-01-26 00:00:00 UTC to 2026-01-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 00:00:00 UTC to 2026-01-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-28 00:00:00 UTC to 2026-01-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-29 00:00:00 UTC to 2026-01-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-30 00:00:00 UTC to 2026-01-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-31 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-02-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 00:00:00 UTC to 2026-02-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-03 00:00:00 UTC to 2026-02-04 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsFeb 3

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 172026-01-17 00:00:00 UTC2026-01-18 00:00:00 UTC413
Jan 182026-01-18 00:00:00 UTC2026-01-19 00:00:00 UTC101
Jan 192026-01-19 00:00:00 UTC2026-01-20 00:00:00 UTC202
Jan 202026-01-20 00:00:00 UTC2026-01-21 00:00:00 UTC000
Jan 212026-01-21 00:00:00 UTC2026-01-22 00:00:00 UTC000
Jan 222026-01-22 00:00:00 UTC2026-01-23 00:00:00 UTC000
Jan 232026-01-23 00:00:00 UTC2026-01-24 00:00:00 UTC000
Jan 242026-01-24 00:00:00 UTC2026-01-25 00:00:00 UTC000
Jan 252026-01-25 00:00:00 UTC2026-01-26 00:00:00 UTC000
Jan 262026-01-26 00:00:00 UTC2026-01-27 00:00:00 UTC000
Jan 272026-01-27 00:00:00 UTC2026-01-28 00:00:00 UTC000
Jan 282026-01-28 00:00:00 UTC2026-01-29 00:00:00 UTC000
Jan 292026-01-29 00:00:00 UTC2026-01-30 00:00:00 UTC000
Jan 302026-01-30 00:00:00 UTC2026-01-31 00:00:00 UTC000
Jan 312026-01-31 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 12026-02-01 00:00:00 UTC2026-02-02 00:00:00 UTC000
Feb 22026-02-02 00:00:00 UTC2026-02-03 00:00:00 UTC000
Feb 32026-02-03 00:00:00 UTC2026-02-04 00:00:00 UTC312

What Hacker News says

10 sources
Irrelevant question. In README has: >Built in public as a learning-by-doing project So, either the entire project was already written and being uploaded one file at the time (first modification since lowest commit mentioned is README update: https://github.com/whispem/minikv/commit/6fa48be1187f596dde8..., clearly AI generated and clearly AI used has codebase/architecture knowledge), and this claim is false, or they're implementing a new component every 30s.
In Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
whispem·Feb 3, 2026Submission

Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)

Hi HN, I'm Emilie, I have a literature background (which explains the well-written documentation!) and I've been learning Rust and distributed systems by building minikv over the past few months. It recently got featured in Programmez! magazine: https://www.programmez.com/actualites/minikv-un-key-value-st... minikv is an open-source, distributed storage engine built for learning, experimentation, and self-hosted setups. It combines a strongly-consistent key-value database (Raft), S3-compatible object storage, and basic multi-tenancy. Features/highlights: - Raft consensus with automatic failover and sharding - S3-compatible HTTP API (plus REST/gRPC APIs) - Pluggable storage backends: in-memory, RocksDB, Sled - Multi-tenant: per-tenant namespaces, role-based access, quotas, and audit - Metrics (Prometheus), TLS, JWT-based API keys - Easy
Read the rest
to deploy (single binary, works with Docker/Kubernetes) Quick demo (single node): ```bash git clone https://github.com/whispem/minikv.git cd minikv cargo run --release -- --config config.example.toml curl localhost:8080/health/ready # S3 upload + read curl -X PUT localhost:8080/s3/mybucket/hello -d "hi HN" curl localhost:8080/s3/mybucket/hello Docs, cluster setup, and architecture details are in the repo. I’d love to hear feedback, questions, ideas, or your stories running distributed infra in Rust! Repo: https://github.com/whispem/minikv Crate: https://crates.io/crates/minikv
71 points · Open discussion
I just don't see the point of denying that. People use LLMs for coding for sure and it is not a bad thing, and no one can automate a full project 100% with LLMs. What I saw is that you created initial commits one file at a time via GitHub's web UI, with multiple follow-up commits just to remove emojis from your scripts: https://github.com/whispem/minikv/commit/c611897f05235ea4410... https://github.com/whispem/minikv/commit/59369fcbb2a94c5dd07... https://github.com/whispem/minikv/commit/0e86e9e328b21170e77... https://github.com/whispem/minikv/commit/9a4cedcd30c3a00e7ea... Care to share why those emojis were there in the first place? I guess the next step is to say the Rust codes are 100% handwritten but scripts/docs are AI-assisted? ;)
In I went from literature/language to Rust systems programming in under a year
Hi HN, I’m Emilie (Em’ on GitHub: https://github.com/whispem). My background is in literature and linguistics – I spent most of my pre-2025 life far away from computers. I really started programming in January 2025 through the Apple Foundation Program, where I learned Swift, UI/UX design, and how to build basic iOS apps—even though everything felt new and visual at first! That playful intro made me realize I could actually learn to code, so I kept pushing my limits. Since October 27th, 2025, I’ve been diving deep into Rust and systems development, building projects as a way to understand storage engines, distributed systems, and even the basics like command-line tools. I was even invited to give a talk about my learning journey and beginner perspective at Epitech Marseille on December 16th, 2025, which was an amazing (and slightly terrif
Read the rest
ying) experience! My approach is always “learn by building” – no formal CS background, just a lot of note-taking, self-challenges, reading docs, and sharing code/experience in public. If you’re curious about how a non-traditional background can be (sometimes!) an advantage for learning technical skills, or if you’re coming to Rust/systems from outside tech, I wrote down my full path and lessons learned here: https://github.com/whispem/minikv/blob/main/LEARNING.md Always happy to connect, share tips for nontraditional learners, or just chat about the joys and headaches of learning Rust and low-level systems from scratch. You can find everything (good and bad!) on my GitHub profile. – Em’
In I went from literature/language to Rust systems programming in under a year
Ok, let me call you out more explicitly. It is clear that most of the code is not written by you. Commit history shows that first a large feature appears out of the blue, then you have a followup series of commits removing "useless" comments (left by LLM). Quite a few useless comments are still there. Also your rust implementation is 100% broken which some of comments you deleted point out. I also love this comment: https://github.com/whispem/minikv/blob/main/src/coordinator/... It is exactly what LLMs write when you ask them to implement something.
In Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
whispem·Jan 17, 2026Submission

Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)

Hi HN, I’m releasing minikv, a distributed key-value and object store in Rust. What is minikv? minikv is an open-source, distributed storage engine built for learning, experimentation, and self-hosted setups. It combines a strongly-consistent key-value database (Raft), S3-compatible object storage, and basic multi-tenancy. I started minikv as a learning project about distributed systems, and it grew into something production-ready and fun to extend. Features/highlights: - Raft consensus with automatic failover and sharding - S3-compatible HTTP API (plus REST/gRPC APIs) - Pluggable storage backends: in-memory, RocksDB, Sled - Multi-tenant: per-tenant namespaces, role-based access, quotas, and audit - Metrics (Prometheus), TLS, JWT-based API keys - Easy to deploy (single binary, works with Docker/Kubernetes) Quick demo (single node): git
Read the rest
clone https://github.com/whispem/minikv.git cd minikv cargo run --release -- --config config.example.toml curl localhost:8080/health/ready # S3 upload + read curl -X PUT localhost:8080/s3/mybucket/hello -d "hi HN" curl localhost:8080/s3/mybucket/hello Docs, cluster setup, and architecture details are in the repo. I’d love to hear feedback, questions, ideas, or your stories running distributed infra in Rust! Repo: https://github.com/whispem/minikv Crate: https://crates.io/crates/minikv
35 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.