Time Is a Lie !?

When things happen on different computers, how do you know what happened first? One group chat, one question: how a server stamps your message, why clocks fail (drift, NTP, Cloudflare's 2017 leap second outage, last-write-wins data loss), then what replaces them, step by step: cause and effect, Lamport timestamps, vector clocks as a scoreboard of what each side has seen, hybrid logical clocks, and Spanner's TrueTime commit wait. 0:00 How a chat message travels 1:52 Why two clocks never agree 4:46 When time ran backwards 6:52 The save that vanished 8:26 The rule that needs no clock 10:11 Numbers instead of times 12:02 A scoreboard of what you've seen 14:31 Getting real time back 15:41 Waiting out the doubt 17:30 What to do on Monday 18:25 Remember Sources and further reading: • Lamport, Time, Clocks, and the Ordering of Events in a Distributed System (1978) • Corbett et al., Spanner: Google's Globally-Distributed Database (OSDI 2012) • DeCandia et al., Dynamo: Amazon's Highly Available Key-value Store (SOSP 2007) • Kulkarni et al., Logical Physical Clocks and Consistent Snapshots in Globally Distributed Databases (2014) • Cloudflare: How and why the leap second affected Cloudflare DNS (2017) • Discord: How Discord Stores Billions of Messages; Discord API reference, Snowflakes • Telegram API docs: Working with Updates (message ID sequences) • Twitter Snowflake design notes (system clock dependency) • Go proposal 12914: Monotonic Elapsed Time Measurements • Google Public NTP: Leap Smear • CockroachDB docs and blog: clock management, max offset 500 ms • AWS: Amazon Time Sync Service and ClockBound • Euronews, 16 Oct 2026: CGPM ends leap seconds from 20 May 2027 Latent — the hidden side of software. Real problems, why the obvious fix fails, and what actually works. #distributedsystems #systemdesign #softwareengineering