We're using riak_dt in anger in our product. We are already using it with rebar3, and Erlang 18.3 through some super messy patches.
I would love to see a register that takes the logical clock, and timestamp for resolution, rather than just a straightup timestamp. My biggest ask though is delta-CRDTs. Delta-CRDTs with a decent anti-entropy algorithm would allow our system to scale from 1000s of keys to 100ks of keys. Nonetheless, Riak_dt is an awesome library, and we're probably planning on contributing back to it soonish, especially if any of the other comments on this thread are things we need, and Basho doesn't. On Thu, Apr 28, 2016 at 12:55 AM, Russell Brown <russell.br...@me.com> wrote: > Hi, > Riak DT[1] is in need of some love. I know that some of you on this list > (Sargun, are you here? Heinz?) have expressed opinions on the work that needs > doing. Here is my short list, I would love to hear opinions on priority, and > any additions to this list: > > 1. merger smaller map branch > 2. deltas > 3. new data types (we have a range register and some and Multi-Value-Register > to add, any more?) > 4. Internal state as records or maps (but not these messy tuples) > 5. update to rebar3 > 6. update to latest erlang > > I’m pretty sure there is plenty more. Would greatly appreciate your feedback. > > Many thanks > > Russell > > [1] https://github.com/basho/riak_dt/ > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
