Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynomite project is dead ? #793

Open
jyriok opened this issue May 4, 2021 · 4 comments
Open

Dynomite project is dead ? #793

jyriok opened this issue May 4, 2021 · 4 comments

Comments

@jyriok
Copy link

jyriok commented May 4, 2021

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 :)

@morganbst
Copy link

morganbst commented Jun 6, 2021

+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!

@mcouillard
Copy link

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.

@m-ueberall
Copy link

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?

@mcouillard
Copy link

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants