3 ms·
Eventual consistency violates the principle of least surprise. "Oh you hit the save button? Yah, we'll get to that."
by exabrial 13y ago
Eventual consistency violates the principle of least surprise.
"Oh you hit the save button? Yah, we'll get to that."
- Terr_ 13y agoThat's not what it means. The save is understood and complete, the unknown part is whether someone else's revision will take priority or whether it'll cycle to some other state.
- Nacraile 13y agoEventually consistent systems aren't built because eventual consistency is considered a "good" property. Eventually consistent systems are built because eventual consistency is the least-bad option in a fundamental trade-off. When a distributed system is partitioned, it is impossible to execute all operations on a shared resource serializably. So, the system must either fail some requests, or fail to be serializable. You can have your principle of least surprise, or you can have a system that is capable of serving traffic even after some drunk sailor drags an anchor through a submarine cable. You can't have both.
- pjc50 13y agoHitting the save button is fine; the problem is more when one person hits "save" and the other person hits "cancel" at the same time. There can be only one winner.