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

Will nebulex support replicating cache partitions? #47

Closed
queer opened this issue Apr 19, 2019 · 4 comments
Closed

Will nebulex support replicating cache partitions? #47

queer opened this issue Apr 19, 2019 · 4 comments

Comments

@queer
Copy link

queer commented Apr 19, 2019

I'm sorry if this has been asked before; I couldn't find it with a quick search.

My question is pretty much just the title. I have a real use-case for wanting to be able to replicate partitions - as a full replication à la #15 would require too much RAM usage - and I also don't have the brain power time/knowledge to write a partition replicator that I would have any confidence in. I'm also somewhat curious if this effect can be created by just running two Dist caches per node - I feel like it might work but also might just double the data being stored on each node with no real gain.

@queer
Copy link
Author

queer commented Apr 20, 2019

Never mind; I think my problem would be more suited to something like riak_core.

@queer queer closed this as completed Apr 20, 2019
@cabol
Copy link
Owner

cabol commented Apr 22, 2019

@queer about your question, yes, Nebulex will eventually implement replicated topology via #15 (adapter).

I have a real use-case for wanting to be able to replicate partitions - as a full replication à la #15 would require too much RAM usage

Indeed, actually memory consumption is one of the downsides of the replicated topology.

and I also don't have the brain power time/knowledge to write a partition replicator that I would have any confidence in. I'm also somewhat curious if this effect can be created by just running two Dist caches per node - I feel like it might work but also might just double the data being stored on each node with no real gain.

NP, thanks for the interest :)!! Replicated topology impl is in progress now (we hope to have a first draft very soon), and I'm thinking to implement a mnesia adapter, which will give us the ability to setup different topologies, not only full-replicated but also partitioned topology with better failover mechanism using replicas (via mnesia fragments maybe?).

Never mind; I think my problem would be more suited to something like riak_core

Indeed, riak_core is another option to implement it – actually, it would be nice to have an adapter using riak_core :)

@queer
Copy link
Author

queer commented Apr 28, 2019

As it turns out, I've come full-circle back to looking at Nebulex, as I've not been able to get riak_core working 😅

@cabol
Copy link
Owner

cabol commented Apr 29, 2019

😄 Yeah, get riak_core working may be a bit tricky. If you want to continue with riak_core, perhaps I have a couple of projects that might help: erlbus v0.1.0 and west. But anyways, the mnesia adapter is in progress, I hope to publish a draft version very soon.

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

2 participants