What is the 'happened-before' relationship and why does it matter?
Event A happened-before event B if A's vector is less-than-or-equal to B's vector (elementwise), and they differ. This proves A was in B's causal past—likely because A sent a message to B or through an intermediary. Respecting happened-before ensures consistency.
Answered in
Vector Clocks: Detecting Causality in Distributed SystemsVector clocks solve distributed ordering: when wall-clock timestamps fail to detect concurrent writes, vector clocks reveal true causality and conflicts.
Read the full analysisOther questions this article answers
More system design questions
- Why doesn't Google just run Dijkstra faster?
- What is a shortcut edge and when is it precomputed?
- How much space do shortcut edges take compared to the original graph?
- Can Contraction Hierarchies handle dynamic graphs like traffic or road closure?
- Why contract low-degree nodes first instead of high-degree ones?
- What is a CRDT and why does it matter for real-time collaboration?
- How do CRDTs handle concurrent edits without a central server referee?
- Why did Figma move from operational transforms to CRDTs?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design beat.