Re:NewSQL databases fail to guarantee consistency and I blam...
by apoverton on Friday September 21, 2018 @12:21PM
(#18040768)
I think if 2 events are independent then you can use an eventually consistent DB like Cassandra and move on with your day. The importance of something like TrueTime arises when you have an example like in the article. Step 1: remove your parents from seeing your photo albums. Step 2: post your spring break photo album
Re:NewSQL databases fail to guarantee consistency and I blam...
by taeric on Friday September 21, 2018 @01:18PM
(#18041177)
That doesn't sound like a system you need "true time" for. :(
Of course, I think I just like thinking about how true time will start to fail once we get beyond the earth. Consider, what is the true time for events we are seeing in the stars right now?
Granted, I fully cede that being able to rely on a fully sequenced notion of time that everyone is a part of makes some reasoning much easier.
Re:NewSQL databases fail to guarantee consistency and I blam...
by sseth on Friday September 21, 2018 @12:23PM
(#18040776)
TrueTime is not a timestamp, but a time with a spread which reflects the maximum difference in time between two data centers.
If i understand correctly, if the size of this increases too much, this brings down the number of transactions per second which can be done, so keeping the spread small is key. Hence the atomic clocks etc.
If two events are independent, it matters very little what order we record them in the system of record.
My whole career we have been building cause and effect at transaction time but when we debug we stare at log files and time stamps like we are reading tea leaves, trying to figure out what situation A led to corrupted data in row B.
Maybe there’s a way to record this stuff instead of time stamps? Something DVCS style. Or maybe it’s provably intractable.