3 ms·
I feel like the "sweeping under the rug" is being done here by way of engineering compromises (assumptions & bounds). The compromise in this case happens to be
by bob1029 5y ago
I feel like the "sweeping under the rug" is being done here by way of engineering compromises (assumptions & bounds).
The compromise in this case happens to be something along the lines of "If the GPS constellation fails, TrueTime fails (or gets really slow)". For better or worse, all of these TrueTime-style products (AWS has one now too), are effectively dependent on GPS to provide a global synchronous context. I don't think there is any feasible way to bootstrap or maintain a distributed clock with higher precision than its terrestrial network links would otherwise allow.
The way I look at this, the GPS constellation contributes to the core of these database engines. It provides the most essential identity for all transactions (precise & unique timestamps). The actual database servers are just storing the data and ensuring transactions are interleaved properly.
It is probably reasonable from a practical perspective to align your failure modes with those of other telecom and military organizations.
- vvern 5y ago> “If the GPS constellation fails, TrueTime fails (or gets really slow)". To deal with this threat model, spanner has atomic clocks in each data center, named “Armageddon time masters”, the most badass name of a component in any distributed system I know of.