HNHacker News
TopNewBestAskShowJobs

whispem

55 karma · joined November 24, 2025

Founder & Maintainer @ WhispHub | Rust Developer (minikv, Whispem-lang) | Data Science Student @ AMSE
submissionscomments
whispem··on Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
Thanks!
whispem··on Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
Nope, it’s all me—both code and comments :) If you want to review something technical, I’m happy to chat!
whispem··on Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
No AI involved here—just me doing my best to be clear and thoughtful in my replies.
whispem··on Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
Thanks for the insight!

You’re absolutely right—the distributed KV/object storage space is very mature, and I don’t expect to “out-innovate” the current leaders. My main goal is to learn by reimplementing challenging systems from (almost) scratch and to deeply understand how these pieces work behind the scenes.

LLM infra is definitely a hot frontier—makes sense that it’s where lots of cutting-edge work is happening. Maybe someday I’ll try my hand at that too. For now, I want to really master the fundamentals!

Thanks again for your perspective—it’s helpful to think about where the opportunities (and weeds!) are.

whispem··on Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
Haha, thanks!

I like the clarity of the real arrow—it just makes flows in comments more readable for me.

Glad to see someone noticed!

whispem··on Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
Thanks a lot for the suggestion and the link!

I’m mainly building minikv to learn more about real-world distributed storage and consensus—and to see how far I can take it as a personal project. Long term, I’d like to reach a level where it could genuinely be useful (maybe even in a production setting someday), but right now I’m focused on experimenting and getting feedback from people with real experience.

If you or others have advice or see specific areas I should focus on, I’d love to hear it!

whispem··on Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
Good question!

All the code, architecture, logic, and design in minikv were written by me, 100% by hand. I did use AI tools only for a small part of the documentation—specifically the README, LEARNING.md, and RAM_COMMUNITY.md files—to help structure the content and improve clarity.

But for all the source code (Rust), tests, and implementation, I wrote everything myself, reviewing and designing every part.

Let me know if you want details or want to look at a specific part of the code!

whispem··on Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
Thanks for the kind words and for the “beginners” encouragement—totally agree, it’s easy to lose sight of that!

I get the point about feature creep. I started “small,” then kept adding features as a way to learn and push my limits. My goal is to keep the design modular enough so people can use just the parts they need.

If you (or anyone else) would be interested in a stripped-down mode or a build with fewer features, I’d love to hear what that would look like to you!

Thanks again for the thoughtful feedback.

whispem··on Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)
Thanks a lot for your comment!

I’ve put a lot of work into this over the past year—learning from established open source projects and carefully testing every feature to build something robust and reliable. For now, this is still a passion and learning project, but I do hope that, eventually, it can mature enough to be used in real-world production—maybe even in enterprise contexts someday.

There’s still a long way to go, and I’m definitely open to feedback and suggestions from anyone who’d like to help me improve.

← PreviousPage 2 of 2