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)