For my project I need a deep understanding of how Meteor handles conflict resolution at the record level.
Does it use OT, diff-merge or something simpler like last edit wins?
If it helps, the problem i’m trying to solve is: In my scenario I will have multiple users (~10) subscribed to the same collection record. The record could be a complex JSON structure. In its basic form, the structure represents a deck of cards like a Trello list - except in my case the deck has parent (group) and child cards. Each user may make non-trivial changes to the deck (i.e. change the sequence of the parent cards (thus moving all children) as well as changing details of each child card. In this case. how will Meteor behave if multiple users change the sequence of cards at the same time?