Dynomite project is dead ?
jyriok opened this issue · 4 comments
hello,
We use Dynomite here but we don't see any major upgrade since 2019 (except one little bugfix this january)
Netflix use another technologies than Dynomite with Redis ? what is the futur for Dynomite ?
thanks for your answers :)
+1 to this question. I've been shopping around for something that can handle global replicate full-active (on all nodes - which counts out a lot of great solutions for which a single region is the "writer" per each record.
Would people still suggest looking at this for a distributed caching solution (basically an in-memory dynamodb from my understanding) The fact that it supports Redist with CRDTs turned on is really appealing to me,
All that being said, I have been looking at EVCache (we noticed the commit graph explode when the Dynomite one fell off. This seems like a really great architecture overall.
It seems like EVCache is fast to just evict and reload (which is probably a much easier pattern than managing state based CRDT updates across multiple regions. Any thoughts from anyone on the real world A/B comparison of those approaches?
Would anybody from Netflix be comfortable sharing how much Dynomite is running in your production environment and any other commentary / context that could be shared. Thank you!
I've been watching https://keydb.dev/ for a while now. It looks like a solid alternative to redis+dynomite for multi-master. But we haven't taken a deep dive to try it yet.
I've been watching keydb.dev for a while now. It looks like a solid alternative to redis+dynomite for multi-master. But we haven't taken a deep dive to try it yet.
@mcouillard Thanks a lot for the link! Did you manage to try it in the meantime?
@m-ueberall We haven't had the need to just yet. And honestly, reading the open Issues on KeyDB today has me a bit worried about their active/active master/master replication. A move to KeyDB likely needs extra thorough testing all the way through real world load testing over time.
Dynomite, while older and not frequently updated, seems to be perfectly simple enough to just plain work reliably for common usage of Redis (v3) commands.