zlacker

>>pharkm+(OP)
I don't get how clocks are bad this from the article.

I get that syncing clocks across systems is hard and when it goes awry, unintended consequences are incurred.

>>dustin+A6
There is, in fact, a TL;DR at the end:

> If your distributed database relies on clocks to pick a winner, you’d better have rock-solid time synchronization, and even then, it’s unlikely your business needs are served well by blindly selecting the last write that happens to arrive.

>>RickHu+29
In fact I would recommend GPS calibrated hardware clocks with PTP.

>>ssever+rj
As last summers negative leap second fiascos demonstrated even a trusted source isnt enough.

>>donava+Yp
They are when you know that the leap-(nanosecond/second/minute/day) is coming up. When you know it is coming, you can "smear" the time difference over, let's say, the entire year, so when it happens, every system behaves correctly.