3 ms·
The point is not that time synchronization is inherently bad, only that it's usually not the correct thing for a distributed database to resolve update conflict
by marshray 13y ago
The point is not that time synchronization is inherently bad, only that it's usually not the correct thing for a distributed database to resolve update conflicts with.
- sseveran 13y agoYes I completely agree. I fail to see how anyone would think that using a clock as a source of truth in a distributed system would be in anyway a good idea. As far as PTP it would be too expensive to deploy at large scale which was some of the motivation (i believe) behind truetime.
- marshray 13y agoTo be fair, time was considered to provide a pretty universal total ordering up until fairly recently, i.e., 1903.