Skip to content

Rahul Suryawanshi

  • Home
  • Technology
    • Distributed Systems
    • System Design & Architecture
    • Platform Engineering
    • Cloud & DevSecOps
    • AI & Generative AI
    • Quantum Computing
  • Distributed Systems
    • Series Overview
    • Part 1 — Foundations
      • What Is a Distributed System?
      • System Models
      • Network Model
      • Failure Model
      • Time Model
    • Part 2 — Communication & Coordination
      • Reliability & Retries
      • Service Discovery
      • Distributed Locks
      • Coordination Services
    • Part 3 — Replication, Consistency & Consensus
      • Consistency Models
      • CAP Theorem
      • Paxos vs Raft
      • Quorums & Voting
    • Part 4 — Fault Tolerance & High Availability
      • Fault Tolerance vs High Availability
      • Failure Detection
      • Observability
    • Part 5 — Scalability & Performance
    • Eight Fallacies of Distributed Computing
  • Engineering Leadership
  • About
    • Experience
    • AI Journey
    • Balto
    • Travel Stories
  • Contact

Causality

Time Model – Why Ordering Is Harder Than It Looks

April 9, 2026January 8, 2026 by Rahul Suryawanshi

In distributed systems, time is not shared. Ordering events requires reasoning about causality, not clocks.

Categories Distributed Systems Tags Causality, Distributed Systems, Event Ordering, Foundations, Happens Before, Logical Clocks, Reliability Engineering, System Design, Time Model, Vector Clocks
  • Technology
  • Distributed Systems
  • System Design
  • Platform Engineering
  • Engineering Leadership
  • About
  • Contact
© 2026 Rahul Suryawanshi • Built with GeneratePress
 

Loading Comments...