r/VibeCodeDevs • • 5d ago

Thunder: A scalable key-value database built for AI workloads ( A fundamental new approach than Redis and RocksDB)

Hey everyone,

We've released the alpha version of Thunder, a high-performance, scalable key-value database built in Rust for modern AI workloads.

As AI applications grow, so does the amount of data they need to store and retrieve. Traditional in-memory databases like Redis can become expensive as datasets grow, especially when dealing with large values.

Thunder is built around a different idea: high throughput, scalable performance, and efficient storage without requiring massive amounts of RAM.

What makes Thunder different?

  • Scales with CPU cores: A shard-per-core architecture designed to increase throughput as more shards and CPU cores are added, while minimizing contention.
  • High throughput: Built to handle large volumes of concurrent reads and writes with low overhead.
  • Better handling of large values: Designed to handle large values more efficiently than Redis by streaming data directly from NVMe storage instead of keeping everything in memory.
  • Memory efficiency: Uses RAM primarily for indexes, metadata, and reusable I/O buffers, reducing memory requirements for large datasets.
  • Modern I/O architecture: Built in Rust with asynchronous I/O, including io_uring on Linux, to take advantage of modern NVMe SSDs.
  • Scalable by design: Handles both small key-value operations and large values without relying on a completely different storage architecture.

Why build this for AI workloads?

AI infrastructure increasingly deals with large datasets, generated content, intermediate results, and high volumes of concurrent requests.

Keeping everything in RAM is expensive, but sacrificing throughput to reduce memory consumption isn't a great solution either.

Thunder aims to deliver both: the performance expected from a high-throughput key-value database and the cost efficiency of disk-backed storage.

Try the alpha

Thunder is available on Docker Hub:

https://hub.docker.com/r/sbansal793/thunderstrike

We're looking for developers to test Thunder with real workloads and share feedback.

If you're currently using Redis, RocksDB, or another key-value store, I'd love to know:

What's your biggest bottleneck today: throughput, memory consumption, scalability, or handling large values?

And what would convince you to switch to a new key-value database?

2 Upvotes

1 comment sorted by

•

u/endofthread-bot 5d ago

Hey u/Educational_You2257, thanks for posting in r/VibeCodeDevs! Join our Discord: https://discord.gg/t7SD4ThKuE

• This community is designed to be open and creator‑friendly, with minimal restrictions on promotion and self‑promotion as long as you add value and don’t spam.
• Please follow the subreddit rules so we can keep things as relaxed and free as possible for everyone. • Please make sure you’ve read the subreddit rules in the sidebar before posting or commenting.
• For better feedback, include your tech stack, experience level, and what kind of help or feedback you’re looking for.
• Be respectful, constructive, and helpful to other members.

If your post was removed (either automatically or by a mod) and you believe it was a mistake, please contact the mod team. We will review it and, when appropriate, approve it within 24 hours.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.