Thanks again Roland, most helpful.
Stating the schemes in Akka Cluster documentation would be invaluable. My
guess is this would prevent some potentially unsound homegrown solutions.
Just listing the basics (i.e. the majority quorum approach, RAFT, etc)
might prevent a few of these cases,
Great summary Roland.
We should definitely give tools to model the different guarantees. It's not
just Raft/Paxos-style OR full eventual consistency. It's an axis as you
say. Riak gives you some flexibility with its R/W values. For the
interested I recommend reading Peter Bailey's HAT paper and
Thanks Roland!
I read Distributed Systems for Fun And
Profithttp://book.mixu.net/distsys/single-page.htmla few weeks ago. It has a
diagram that was very helpful for me in
understanding the difference between the various types of replication
systems:
Thanks for the thoughtful reply Ronald!
On Tue, May 6, 2014 at 11:58 PM, Akka Team akka.offic...@gmail.com wrote:
Hi Shikhar,
thanks for sharing!
There are many possible ways of dealing with partitions in a distributed
system, and it depends very much on the use-case what the best
That is a really good summary, Roland. This should go into docs or at least
a blog post?
-Endre
On Tue, May 6, 2014 at 8:28 PM, Akka Team akka.offic...@gmail.com wrote:
Hi Shikhar,
thanks for sharing!
There are many possible ways of dealing with partitions in a distributed
system, and it
I have been hacking on a discovery plugin for
elasticsearchhttps://github.com/shikhar/eskka using
akka cluster and I wanted to add some automated downing, and the
auto-down-unreachable-after is not really an option since it can lead to
split brain.
So I went with the approach of using a
