Eventual Inconsistency
Mar. 12th, 2015 08:18 pm> One example of this is any distributed database with a "last write wins" policy for resolving conflicting writes.
Since we already know that "last" by itself is a meaningless term for the same reason that "now" is not a simple value across the whole system, this is really a "many writes, chosen unpredictably, will be lost" policy — but that wouldn't sell as many databases, would it?
Even if the state of the art is still rapidly improving, anyone should be able to do better than this.
Since we already know that "last" by itself is a meaningless term for the same reason that "now" is not a simple value across the whole system, this is really a "many writes, chosen unpredictably, will be lost" policy — but that wouldn't sell as many databases, would it?
Even if the state of the art is still rapidly improving, anyone should be able to do better than this.