Re:Dragonflydb – A modern replacement for Redis and Memcached
by romange on Monday May 30, 2022 @01:51PM
(#31561608)
Unfortunately unlikely. Shared nothing architecture works with messaging. So threads send each other messages like "give me the contents of that key" or "update this key". Operations like SET/GET will require a single message hop. Operations like RENAME require 2 hops. Transactions and Lua scripts will require number of hops as number of operations in the transactions. When it's in the same process - the latency penalty in negligible. But between different machines - you will feel it. But who knows, AWS already have very cool UDP-like protocol with very low latency... if this will become the standard inside cloud environments maybe we can create a truly distributed memory store that spans multiple machines transparently.
[ Parent
| on HN ]
Re:Dragonflydb – A modern replacement for Redis and Memcached
by etaioinshrdlu on Monday May 30, 2022 @02:32PM
(#31562070)
The latency would be worse, but would the throughput still scale pretty much linearly? It might still be super useful.
Re:Dragonflydb – A modern replacement for Redis and Memcached
by romange on Monday May 30, 2022 @03:35PM
(#31562772)
Yes, VLL algorithm kinda solves the throughput problem. You will still have some issues with fault-taulerance - i.e. what you do if a machine does not answer you.
For intra-process framework it's not an issue (as long as we do not have deadlocks).