kvrocks

How does this compare and benchmark with https://github.com/apache/kvrocks

> Redis (and memcache) are memory caches and should be treated like that If you haven't come across Kvrocks yet, it may be worth a look: https://github.com/apache/kvrocks https://kvrocks.apache.org/ . It's a database with a Redis-compatible wire protocol, but the database is stored on disk. This means your working set is not limited by RAM and can be a few orders of magnitude larger! On modern SSDs this is still very fast. I think it improves the durability story as well. But the big win is the orders of magnitude larger database space. As I've been improving my side project https://totalrealreturns.com/ recently I've ended up using both Redis and Kvrocks together. Redis is great for small global state that needs to be super fast. Kvrocks is great for larger bulk data storage (large precomputed datasets), but also supports a lot of the Re

Sorry if somewhat off-topic, but might help with getting more users. Redis is actually good enough and easy to install for most projects, but it has downside that it's "memory-only" (needs to fit in ram), and if you're in a tight container/vm – you'd better not rely on it solely. So, there's another project – called kvrocks https://github.com/apache/kvrocks , which is for people which don't need in-memory perf of redis but would like to use its protocol and be still very performant. However, its devs never packaged a release in deb and other formats. So, if you were to implement something similar ^ which will implement the protocol, have ability to grow on disk, and be available in distro repos (ideally) – would definitely hold a niche of many little projects which benefit from redis-like thing I've done.

The GitHub Readme seems easier to understand: https://github.com/apache/kvrocks?tab=readme-ov-file

Other API-compatible reimplementations (others?): https://github.com/dragonflydb/dragonfly DragonflyDB (not open source, BuSL-1.1) with more performance https://github.com/apache/kvrocks Apache Kvrocks (Apache-2.0) uses disk-based NoSQL database to lower memory usage

If you're looking for a Redis-compatible key-value store, kvrocks[1][2] is an excellent choice. We've used it in many projects, and it's proven to be very stable. Since it's based on RocksDB, it doesn't have the memory limitations of Redis and the license delirium ;-) [1] https://kvrocks.apache.org/ [2] https://github.com/apache/kvrocks

I switched from SSDB to Kvrocks recently, because SSDB is abandoned and the author missing for 3 years now. I used to recommend SSDB, but now there's better alternatives available: https://github.com/apache/kvrocks https://github.com/sabledb-io/sabledb

How does it compare to Kvrocks, which use RocksDB as the storage backend too? https://github.com/apache/kvrocks/

Not affiliated (not my first comment about this) but we are using KVRocks[1] for now at work, which is based on RocksDB by Meta and it works nicely. Developers are nice and reactive and the Redis commands support is large. We picked this project because of our RAM usage that was exploding with Redis. The only downside for us right now is the Kubernetes support. There is an operator and a controller being made but no Helm Chart yet to deploy Kvrocks with master and replicas easily. That will be awesome. [1]: https://github.com/apache/kvrocks

Why does the fix work like that - only checking for this one scenario when you decrement by type max? [1] In Solidity, where it's a serious security risk, before the language performed overflow checks itself, library authors would perform the arithmetic operation and then e.g. check if the result is larger than the original value in the case of a positive subtrahend [2]. [1] https://github.com/apache/kvrocks/pull/1581/commits/dc5140dd... [2] https://github.com/KingdomStudiosIO/contracts/blob/51873b574...

And here is an interesting conversation when Binbin came to the Kvrocks community: https://github.com/apache/kvrocks/pull/1581#issuecomment-163... * Me: @enjoy-binbin Out of curiosity, do you have a fuzzer to test out Kvrocks? Your recent great fixes seem like a combo rather than random findings :D * Binbin: They were actually random findings.I may be sensitive to this, doing code review and found them (also based on my familiarity with redis)

For the first time, I know our (Apache Kvrocks, an alternative to Redis on Flash) committer Binbin Wang committed nearly 25% of the commits to the newer Redis version. You can find his contributor for both at: * https://github.com/apache/kvrocks/graphs/contributors * https://github.com/redis/redis/graphs/contributors

https://github.com/dragonflydb/dragonfly is another option. Not a fork but API-compatible reimplementation. https://github.com/apache/kvrocks is another, built on RocksDB, with different tradeoff (availability/durability, clustered)

Another under the radar Apache project I've found myself using is Apache KvRocks https://github.com/apache/kvrocks It's a Redis compatible database on top of RocksDB, so unlike Redis it uses the disk instead of RAM, but you can control how much data is cached in RAM, obviously Kvrocks will be slower than Redis for uncached data. Useful in situations where you want a KV data store that isn't limited by your memory specs but is compatible with everything that speaks Redis.

Worth noting that there is a very broad ecosystem of "Redis protocol compatible" databases that are persistence-oriented. KVRocks: Backed by RocksDB https://github.com/apache/kvrocks Tendis: Backed by RocksDB https://github.com/Tencent/Tendis Tidis: Distributed, backed by TiKV https://github.com/tidb-incubator/tidis