4 ms·
If you're interested in Vector Clocks, here is a much better explanation: https://link.medium.com/PvNkzXcsObb https://link.medium.com/PvNkzXcsObb Basically, i
by mojomark 6y ago
If you're interested in Vector Clocks, here is a much better explanation:
https://link.medium.com/PvNkzXcsObb https://link.medium.com/PvNkzXcsObb
Basically, if you have a distributed logical system (i.e. a system that uses more than processor, possibly processors separated by large distances and in noisy environments), it is very difficult to synchronize all of the clocks in each processor, such that if there is a fault, you will be able to use timestamps to localize the exact root cause of that fault. The solution is simply a clock that increments based on logical events within the system rather than a global real world clock. This is very much the same way time appears to work in our physical universe (i.e. time emerges from cause & effect interactions at the quantum scale as entropy increases - if those events slow down, so does the percieved incrementing of time).
- convolvatron 6y agoI would probably start with Lamport clocks pedagogically: https://en.wikipedia.org/wiki/Lamport_timestamp https://en.wikipedia.org/wiki/Lamport_timestamp
- macintux 6y agoFor anyone really bored, I gave a talk at Midwest.io covering various logical clock concepts. https://youtu.be/b_swtL5bxJg https://youtu.be/b_swtL5bxJg