3 ms·
> Eventually consistent systems allow stale reads of older data plus deleted data for an undefined period of time. If you turn around and issue a write based on
by lmm 6y ago
> Eventually consistent systems allow stale reads of older data plus deleted data for an undefined period of time. If you turn around and issue a write based on that you get inconsistency. Eventually consistent systems do not prohibit this.
An eventually consistent system does prohibit that, because as you say it would lead to inconsistency. If you want to do a write based on a read, you're supposed to express that using the system's abstractions, so that a change in the input will (eventually) be propagated to a change in the output.
> You're talking like there are no downsides to CRDTs. There are huge downsides to them, which is why they're rarely used in practice. Your analysis is only valid in theory.
In my experience the "downside" is that you have to actually take 5 minutes to think about your datamodel. They're very much effective in practice. I use them all the time.