Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


Ah, 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.


Oops lol. I guess that applies to CvRDTs as well, since receiving a given state also means receiving all edits that caused it?




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: