4 ms·
the database does it when partition ends. Its called eventual consistency. The database would use something along the lines of vector clocks.
by VladRussian 15y ago
the database does it when partition ends. Its called eventual consistency. The database would use something along the lines of vector clocks.
- lemming 15y agoThe problem is that in this case the database can only apply some ad-hoc heuristic. In the case of the pocket watch, this will be: the first user to buy it gets the watch, and the second user gets annoyed by an email saying that "the watch we said you bought was actually bought by someone else". There's no magic bullet here - this may be acceptable for some use cases but will not be for others.