SKskylurk·Feb 3, 2026
How does this deleted fix_everything.sh fit in to your story?
https://github.com/whispem/minikv/commit/6e01d29365f345283ec...
In Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)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
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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 7:24:48 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.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 17 | 2026-01-17 00:00:00 UTC | 2026-01-18 00:00:00 UTC | 4 | 1 | 3 |
| Jan 18 | 2026-01-18 00:00:00 UTC | 2026-01-19 00:00:00 UTC | 1 | 0 | 1 |
| Jan 19 | 2026-01-19 00:00:00 UTC | 2026-01-20 00:00:00 UTC | 2 | 0 | 2 |
| Jan 20 | 2026-01-20 00:00:00 UTC | 2026-01-21 00:00:00 UTC | 0 | 0 | 0 |
| Jan 21 | 2026-01-21 00:00:00 UTC | 2026-01-22 00:00:00 UTC | 0 | 0 | 0 |
| Jan 22 | 2026-01-22 00:00:00 UTC | 2026-01-23 00:00:00 UTC | 0 | 0 | 0 |
| Jan 23 | 2026-01-23 00:00:00 UTC | 2026-01-24 00:00:00 UTC | 0 | 0 | 0 |
| Jan 24 | 2026-01-24 00:00:00 UTC | 2026-01-25 00:00:00 UTC | 0 | 0 | 0 |
| Jan 25 | 2026-01-25 00:00:00 UTC | 2026-01-26 00:00:00 UTC | 0 | 0 | 0 |
| Jan 26 | 2026-01-26 00:00:00 UTC | 2026-01-27 00:00:00 UTC | 0 | 0 | 0 |
| Jan 27 | 2026-01-27 00:00:00 UTC | 2026-01-28 00:00:00 UTC | 0 | 0 | 0 |
| Jan 28 | 2026-01-28 00:00:00 UTC | 2026-01-29 00:00:00 UTC | 0 | 0 | 0 |
| Jan 29 | 2026-01-29 00:00:00 UTC | 2026-01-30 00:00:00 UTC | 0 | 0 | 0 |
| Jan 30 | 2026-01-30 00:00:00 UTC | 2026-01-31 00:00:00 UTC | 0 | 0 | 0 |
| Jan 31 | 2026-01-31 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 1 | 2026-02-01 00:00:00 UTC | 2026-02-02 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2 | 2026-02-02 00:00:00 UTC | 2026-02-03 00:00:00 UTC | 0 | 0 | 0 |
| Feb 3 | 2026-02-03 00:00:00 UTC | 2026-02-04 00:00:00 UTC | 3 | 1 | 2 |
What Hacker News says
3 sourcesIrrelevant 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)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