KeyDB now has support with multiple masters when replicating, and It’s a drop in replacement to REDIS.
When KeyDB connects with multiple masters it behaves differently than with traditional replication:
Multiple invocations of the replicaof command will result in adding additional masters, not replacing the current one
KeyDB will not drop its database when sync’ing with the master
KeyDB will merge any reads/writes from the master with its own internal database
KeyDB will default to last operation wins
This means that a replica with multiple masters will contain a superset of the data of all its masters. If two masters have a value with the same key it is undefined which key will be taken. If a master deletes a key that exists on another master the replica will no longer contain a copy of that key.
Source: KeyDB – The faster Redis Alternative
Dynomite and the target storage engine run on the same node. Clients connect to Dynomite, and requests are proxied to either the storage engine on the same node or to Dynomite processes running on other nodes.
Dynomite, inspired by Dynamo whitepaper, is a thin, distributed dynamo layer for different storage engines and protocols. Currently these include Redis and Memcached. Dynomite supports multi-datacenter replication and is designed for high availability.
The ultimate goal with Dynomite is to be able to implement high availability and cross-datacenter replication on storage engines that do not inherently provide that functionality. The implementation is efficient, not complex (few moving parts), and highly performant.
מקור: Netflix/dynomite: A generic dynamo implementation for different k-v storage engines
Also, checkout (alternatives?):