Why auto-increment sequence numbers beat timestamps for ordering transactions

Popularity Index: 4 Updated at 2026-10-17 09:36 UTC

Sites

Related Topics

Reordering a transaction log silently changes what the database believes happened Sorting by local clock time breaks the moment a message crosses a time zone Two events stamped in the same millisecond: which one actually happened first A chain of events is not a chain of causes Granger causality asks whether the past of one series helps predict another Concurrent does not mean simultaneous: some events are simply unordered How Google Docs decides whose keystroke came first when two people type at once Sequence diagrams record who sent what to whom but not what actually caused what A Lamport timestamp of 1 followed by 2 proves nothing about causality What is the butterfly effect in philosophy?

Hot Categories

Featured Categories