Re:NewSQL databases fail to guarantee consistency and I blam...
by Cshelton on Friday September 21, 2018 @10:38AM
(#18039996)
Also, I believe all the major cloud providers provide a "TrueTime" API service. I forgot the name that AWS uses, but you can call it on your EC2 instances and make sure your hosts are all in sync. It's pretty cool.
[ Parent
| on HN ]
Re:NewSQL databases fail to guarantee consistency and I blam...
by otterley on Friday September 21, 2018 @10:48AM
(#18040070)
AFAIK AWS is only offering NTP service with a GPS source (i.e. stratum 1). TrueTime appears to be a service offering that is a step above that in terms of the guarantees it provides.
Re:NewSQL databases fail to guarantee consistency and I blam...
by Cshelton on Friday September 21, 2018 @10:58AM
(#18040158)
Ah, I've never had a use case for anything more accurate than NTP
Re:NewSQL databases fail to guarantee consistency and I blam...
by jandrese on Friday September 21, 2018 @03:56PM
(#18042215)
You may never have built a system that needed it, but LTE cell handoffs require higher precision than NTP can supply. Almost every cell phone in use today benefits from highly precise timing.
This is why PTP and high precision GPS devices are built to integrate with cell provider gear.
Re:NewSQL databases fail to guarantee consistency and I blam...
by fintler on Friday September 21, 2018 @03:39PM
(#18042117)
TrueTime is more of a client side library that utilizes a service like NTPd.
You can implement a toy version of TrueTime with about 60 lines of C which uses a single ntp_gettime call for each of the TrueTime api functions (now, before, after).
If AWS's NTPd service offers drift <= 200 us/s, you could use it for TrueTime.