It easy to forget we all started fresh and learned a lot the first few years.

On topic, this project looks nice but a bit too featureful for my minimalistic taste.

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.

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!

However, all storage is managed locally (in-memory, RocksDB, or Sled) by minikv. It does not use AWS S3 or any cloud storage as a backend; minikv itself stores your data on local disks.

So: applications can use minikv as if it were S3, but minikv stores data locally (not in S3).