Home▸Distributed & Parallel Computing▸Vector Clocks: Ordering Events Without a Shared Clock

🕸️ Vector Clocks: Ordering Events Without a Shared Clock

Learn how vector clocks let distributed machines figure out which events caused which, without ever agreeing on a wall-clock time, and how they can even detect events that happened independently.

Distributed & Parallel Computing3DModerate60 FPS

This simulator visualizes multiple processes exchanging messages and updating their vector clocks in real time, showing exactly when events become causally ordered and when they remain concurrent.

🔬 What It Demonstrates

This simulator visualizes multiple processes exchanging messages and updating their vector clocks in real time, showing exactly when events become causally ordered and when they remain concurrent.

🎮 How to Use

Trigger local events and send messages between processes, then watch each vector update live and compare any two events to see whether one happened-before the other or whether they are concurrent.

💡 Did You Know?

Amazon's Dynamo paper popularized vector clocks in production databases specifically because they could surface genuinely conflicting concurrent writes instead of silently discarding one, letting applications resolve conflicts with real business logic.

⚙ Under the hood

Learn how vector clocks let distributed machines figure out which events caused which, without ever agreeing on a wall-clock time, and how they can even detect events that happened independently.

distributed-systemsvector-clockscausalityconcurrencydynamoversion-controllogical-clockscomputer-science

3D · Three.js / WebGL renderer · 60 FPS target · runs fully client-side, no install