> On Mar 4, 2017, at 4:47 PM, Thiago Alencar <[email protected]> wrote: > > I think it could be a nice idea to expand on that to include CRDT's. Have you > thought about it? or is it the case that the current versioning model > wouldn't fit to that approach ?
Definitely thought about that! CRDTs* would generally be used for individual properties of documents, not as an entire document; so we’d need a resolve/merge API that can operate at the property level. Then you could build your doc’s conflict resolver out of pieces, so for example you could have most properties use a “last update wins” rule based on an updateTime property, except that the “votes” property is a counter CRDT, and the “comments” array should use a set union. We haven’t worked out what the API for this would look like, though. —Jens * https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/F34EB619-C6D8-4EBA-A696-3AB43CD7C3D3%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
