SSDB VS Tendis

I've used SSDB[0] in the past for some really stupid large datasets (20TB)_and it worked really well in production

[0] https://github.com/ideawu/ssdb

> Or wanting to shift the architecture entirely to avoid using memory-bound Redis as a queue with an overflow risk.

I wanted to use SSDB[1] instead of Redis for that reason, but it doesn't support the necessary data structures.

[1] https://github.com/ideawu/ssdb

There is also ssdb https://github.com/ideawu/ssdb

It's 2021 and we have extremely fast key-value lookups using LevelDB/RocksDB, but we're still using RAM-based caching tools [1] [2] [3]. It's time to consider RAM-based caching harmful, and start caching with SSDs for larger datasets and lower costs. For ex: SSDB [4]

[1] https://redis.io/

[2] https://memcached.org/

[3] https://news.ycombinator.com/item?id=29532552

[4] https://github.com/ideawu/ssdb#ssdb-vs-redis

Aside from this particular use-case, which is what most people here are talking about -- I had never heard of the SSDB project, but it interests me because I often use Redis for certain things it's able to do, aside from its in-memory storage, and sometimes the fact that the data is not stored on disk is a bit of a drawback for me, something I have to work around.

There is a project called Tendis, the architecture of IceFireDB is different from it, but they are all based on disk storage and resp protocol. Thank you for your attention and contact at any time

Does anyone have any experience with these other Redis clones? I need to write a benchmark on these someday (the outline for the blog post is already written), but have restricted my yak shaving recently:

- https://github.com/Tencent/Tendis

- https://github.com/Netflix/dynomite

On a separate note, is FLASH supposed to be an acronym? I can't tell if they're referring to flash storage (SSD, NVMe) or they're referring to perhaps a special algorithm that uses flash storage +/- some other features, or some altogether proprietary hardware.