Re:Amazon Time Sync Service
by foota on Thursday November 04, 2021 @05:13AM
(#29104901)
The combination of a time and guaranteed error bound can be used as a primitive in distributed systems. You can get timestamps from requests coming from different systems and relate them in a meaningful way. At least, in a false negative fashion. E.g., if A occurs at T + 100ms with 1ms uncertainty and B occurs at T + 105ms with 2ms uncertainty you can conclude that A happened before B. This does not allow you to always establish an order (e.g., if there is overlap) but this isn't always necessary. For instance if instead you are B and you want to have something occur after some time A with uncertainty A_uncertainty, then you can sleep until B with uncertainty B_uncertainty such that B - B_uncertainty > A + A_uncertainty.
[ Parent
| on HN ]
None of this has to do with Amazon though. I am very uncomfortable with Amazon (or the others) pretending that they invented precision timekeeping and that it is a special feature only they have because it seems like a lot of people believe it and build systems that rely on an API that is proprietary to a cloud vendor rather than just installing ntp.
Traditional systems don't offer the same guarantees, do they?
Yes they do. See thread above: https://news.ycombinator.com/item?id=29104177
Right, but you won't get a _good_ global error bound without doing the same amount of work. Do you have atomic clocks lying around?
Yes I do, an Rb standard. You can buy them on eBay. It’s completely optional and only has any effect when GPS reception is down.
You must know some pretty smart five year olds!