On 01.02.16 10:27, Patrik Nordwall wrote:
Is the causality tracking (the vector clocks) used for anything else than supporting "interactive conflict resolution"? Are they needed when using CRDTs?
Operation-based CRDTs as specified in http://hal.upmc.fr/file/index/docid/555588/filename/techreport.pdf rely on a causal delivery order. More generally, for conflict resolution, you need to distinguish concurrent updates from causally related ones, regardless whether this is done interactively or not. For application-defined convergent data types i.e. CRDTs that use custom domain logic, they are therefore needed as well.
Based on my (incomplete) understanding of Riak's "failed experiments" of exposing vector clocks and letting application/user decide what version to continue with I'm skeptical to that approach. I think the conflict resolution must be automatic, i.e. CRDTs, and then I wonder what the vector clocks adds?
-- Martin Krasser blog: http://krasserm.github.io code: http://github.com/krasserm twitter: http://twitter.com/mrt1nz --
--- You received this message because you are subscribed to the Google Groups "Akka User List" group.Read the docs: http://akka.io/docs/ Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html Search the archives: https://groups.google.com/group/akka-user
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
