Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1
  • 4
    Ah, consistency, that quality that's so poorly understood. Consider this peculiarity: If I make two web requests to the same physical machine, one that just reads data and one that changes data, it's completely valid for the read request sent first to return after the later change request, and yet show the original data. Because latency is a thing. When dealing with shared, mutable state, it's best to start with the assumption that all reads are dirty. All distributing the db really does is increase the figurative time between reads and updates, so things are dirtier longer. Commented Dec 15, 2018 at 9:16