3 ms·
That’s only the case for CmRDTs, right? AFAIK CvRDTs (which send the whole state with every request) don’t impose any constraints on message order.
by jakelazaroff 3y ago
That’s only the case for CmRDTs, right? AFAIK CvRDTs (which send the whole state with every request) don’t impose any constraints on message order.
- fastball 3y agoAh, a bit of an "eats shoots and leaves" situations here. I mean: Yes, CRDTs require all clients receive all edits in order to guarantee convergence. They indeed do not need to be "in order", they merely need to receive all edits "to guarantee convergence". My insertion of "in order" was definitely confusing there.
- jakelazaroff 3y agoOops lol. I guess that applies to CvRDTs as well, since receiving a given state also means receiving all edits that caused it?