> /changes lists all the IDs that might have changed.
How does it do this in a distributed setting? When clients might be connecting to multiple servers with different states?
How does it do this in a distributed setting? When clients might be connecting to multiple servers with different states?
I mean, you can do other things - but at the point where you're switching between multiple masters in a split brain from your client, all bets are off - so you're going to need to fall back resyncing any mutable data.
CRDTs handle split brain fine. They eventually converge. You just don't want your clients flapping in the meantime by resyncing tons of data. That's where a distributed sync algorithm would help keep things working in the interim.