Earlier quoted context omitted.
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 alwa…
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.
Amazon Time Sync Service
91–94 of 94 posts
Re: Amazon Time Sync Service
#92Earlier quoted context omitted.
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?
Re: Amazon Time Sync Service
#93Earlier quoted context omitted.
Traditional systems don't offer the same guarantees, do they?
Yes they do. See thread above: https://news.ycombinator.com/item?id=29104177
Re: Amazon Time Sync Service
#94Earlier quoted context omitted.
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?