28 ms·
It relies on the data being commutative. If the data is not commutative then we need, wait for it, drum roll please, some consistency, which by your own admissi
by sseveran 12y ago
It relies on the data being commutative. If the data is not commutative then we need, wait for it, drum roll please, some consistency, which by your own admission is not provided. The consistency is the hard part which is why there is an entire field of study on just this problem.
I fail to see how your merge algorithm is deterministic in case of failures.
- karlgrz 12y agoYou -cannot- have a distribute database without consistency. Prove us ALL wrong, please.
- marknadal 12y agoMaybe I wasn't clear... GUN does have Eventual consistency, but not strong/global consistency. Aka GUN is AP and Eventually consistent. You manually at the application layer can decide to lock, sacrificing Availability, and get strong consistency. The merge algorithm works in an Eventually consistent case, but obviously is too naive for global Consistency, you'd need some form of consensus. Or does that not address your comment?