> Is it deterministic in a way that's useful? Yes, because it allows to maintain a consistent state across distributed nodes. > From the perspective of the en

> Is it deterministic in a way that's useful? Yes, because it allows to maintain a consistent state across distributed nodes. > From the perspective of the end-user its going to appear random ...but consistent. If every node picks a random revision on conflict, then when multiple clients try to continue editing, they'll end up increasing the conflicts. > The split heals, the system picks B because 500 > 100, but the write you actually want to dominate is A. The user can't control which replica gets hit more often, or when a split happens, so while this might be deterministic inside the DB it is semantically random from the user's perspective. Yeah, but what happens if B picks B, and A picks A? Now the write you're looking for is either there or not there, depending on on which node you're talking to. > how would this look any different to the user? Everything is going to look random to the user, no?