KeyDB VS dynomite

- KeyDB: https://github.com/snapchat/keydb

KeyDB is a fork of (everyone's favourite cache store) Redis, and it's messaging protocol and API is 100% compatible with Redis. What that means is you can just point any Redis client (like Hiredis or redis-rb) at a KeyDB instance, and it'll Just Work™️, with no changes required. The KeyDB selling points are: 1) multi-threading by default, and a lot of work was ploughed in to high performance around multi-threading in KeyDB, 2) compatible with all the features of regular Redis, 3) some advanced features which Redis only offers in it's paid/enterprise version are included for free in KeyDB, and the big one for me is multi-active replication, which is what I'm playing with here.

KeyDB is a multithreading, drop-in alternative to Redis. Keydb-operator easily creates a standalone (1 replica) or a multimaster (3 replicas) KeyDB in-memory database. When KeyDB is in multimaster mode, it is possible to have more than one master, allowing read/write operations to all them. That helps for high availability and fault tolerance.

Have you checked https://keydb.dev/

p.s. another share-worthy Redis alternative is KeyDB https://github.com/EQ-Alpha/KeyDB

I went through the wiki, certainly it was interesting. I believe the implementation is at fastlock.cpp [0], I will go through it. You said earlier:

> If we spin too long the thread will sleep although we wait much longer than any other lock you’ll find.

Did you do any tweaks to mitigate this?

> Generally speaking you don't want to be dealing with this stuff unless you really have to.

Ofcourse. I am just way too curious and excited to learn about these!

[0] - https://github.com/EQ-Alpha/KeyDB/blob/v6.0.16/src/fastlock....

https://github.com/Netflix/dynomite - replication and routing

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.