Hi, delta-CRDTs are very interesting. Contribution to Akka Distributed Data would be much appreciated.
Let me know if you have something I should review or if you want to discuss any design ideas. Probably best if you create an Akka github issue. /Patrik lör 19 nov. 2016 kl. 12:06 skrev Merlijn Boogerd < merlijn.boog...@trivento.nl>: > Hi! For a while now I have developed an interest in developing data-flows > which are non-monotonic (i.e. they support updates and deletes), and > incremental (between batch/stream, within the Spark community this is also > called a continuous application). I have experimented with this in a > separate project and I am now looking to take this to the next step; > building an actual platform out of it. > > I think that at least part of it could be of interest to the Akka and its > community: > 1) I have working versions of the following delta-CRDTs: Enable-Wins-Flag, > Multi-Value-Register, Add-Wins-Set, Remove-Wins-Set and > Observed-Removed-Map from "Delta State Replicated Data Types" by Almeida, > Shoker and Baquero. > I noticed that an earlier paper was referenced in > http://doc.akka.io/docs/akka/current/scala/distributed-data.html. I also > see some tickets referencing this functionality, but they are either closed > or low-priority. I would be willing to try to fit it into distributed-data, > if the interest is there. > 2) I have naive implementations of combinators: map, filter, fold, union, > intersection and product for (an old implementation of) ORSet, from > Christopher Meiklejohns Lasp paper. An implementation for sharded AWSet, > RWSet and ORMap should be feasible and was actually next on my list. A > "scala-collections-feel" to collection-like-CRDTs would be useful and > fitting in Akka, imo. The combinators use is somewhat limited in a > non-sharded memory-only implementation, and I'm not sure how fellow Hakkers > would feel about having them? Adding sharding and persistence is on my > todo-list, and I wonder if an external module is the right way of adding > this functionality to Akka, if of interest at all? > > Disclaimer: my experiments are just that, sloppy, inefficient code that > passes some unit tests for the functionality of interest, but still lacks > an API for proper composition into larger wholes; add to that the common > "it's only a spare-time project, unfortunately" means that nothing of what > I sketched above will be realized any time soon. I'm really just exploring > where my interests fit in the rest of the distributed-systems ecosystem. > Thanks for your attention thus far! > > -- > >>>>>>>>>> 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 > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to akka-user+unsubscr...@googlegroups.com. > To post to this group, send email to akka-user@googlegroups.com. > Visit this group at https://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- >>>>>>>>>> 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 --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
