KiviDB
Ranked 5 of 6 in-memory data stores by recommenders
Recommended as a faster Redis-compatible in-memory database with strong benchmark numbers. Critics say its write pauses grow with key count.
Recommended as a faster Redis-compatible in-memory database with strong benchmark numbers. Critics say its write pauses grow with key count.
9 people gave an opinion
- recommend it
- 7
- criticize it
- 2
- approval share
- 78%
Recommended in 1 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 7 people recommend itNeeds 10 or more, not met.
- 3.5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 1 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Strong benchmark results
“at 100 B GET and pipeline 16, valkey is at 1.61M against 19.71M ops/s for kividb”
Comment from 19 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache” “The benchmark numbers are impressive.”
Comment from 19 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache” “the p99 is sub millisecond”
Comment from 19 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache” Scales across all CPU cores
“With 1.1 we are on par when compared only based on command execution, however it terms of IO kividb performs better.”
Comment from 20 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache” “It is mostly because kividb can utilize all the cores you can allow on a machine”
Comment from 19 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache”
What people warn about
Each mark is one comment
Benchmark fairness questioned
“this benchmark was run on an earlier version of kividb, which still had several memory management issues”
Comment from 19 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache” “Therefore, the test would be biased as the thread pool would become completely starved.”
Comment from 19 Oct 2026 in “Show HN: KiviDB, a faster Redis-compatible memory database and vector cache”
Other in-memory data stores people recommend
The four most recommended other in-memory data stores, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Redis | 174 | 102 | 63% | 12 | 10 yrs7 owners | — |
| Valkey | 31 | 5 | 86% | 10 | — | Approved |
| Memcached | 27 | 10 | 73% | 6 | — | Approved |
| Lux Redis-compatible server | 8 | 7 | 53% | 2 | — | — |
| KiviDBThis page | 7 | 2 | 78% | 1 | — | — |
What people said
12 of the 14 comments that mention it, newest first. Each links to the original comment.
“Performance poor as a cache, redis is 7 times better”
“With 1.1 we are on par when compared only based on command execution, however it terms of IO kividb performs better.”
“the tradeoff is a write pause that grows with key count”
“It is mostly because kividb can utilize all the cores you can allow on a machine”
“Therefore, the test would be biased as the thread pool would become completely starved.”
“The benchmark numbers are impressive.”
“Do let me know if the issues you faced are solved with kividb”
“With lock-based approaches, features like MULTI/EXEC, Lua scripts, and multi-key operations introduce severe contention that becomes hard to manage.”
“the p99 is sub millisecond”
“this benchmark was run on an earlier version of kividb, which still had several memory management issues”
“I thought this project was interesting so I went to the blog and noticed I was reading AI”
“at 100 B GET and pipeline 16, valkey is at 1.61M against 19.71M ops/s for kividb”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.