Distributed systems are hard to test because partial failures overlap with live traffic and the same fault can produce different execution traces on different runs. Unmesh Joshi describes how deterministic simulation testing addresses this by replacing real clocks, networks, and storage with simulated components driven by a single-threaded execution loop. This allows simulating both hard failures and routine slowdowns—such as network and disk latency spikes—and more importantly makes every execution reproducible. This article explains the technique using a quorum key-value store as a running example, with code from Tickloom, a Java implementation of the approach.
Current
·
C2
·2026-11
Deterministic Simulation Testing
Find Your Interest
- Will Wilson on Deterministic Simulation Testing
- Long-horizon agents and durable execution
- Debunking AI agent accessibility claims and solving AI alignment for accessibility
- Agentic Testing: Where Agents Fit in the E2E Testing Stack
- In a deterministic simulation, you can debug with time travel
- Otakar Nieder on Gaming vs Simulation Engines
- Give Your Easter Eggs a Different Spin This Year with These Twisted Spider-Bunny Eggs
- Key Differences in Maintenance Types
- Michigan State dealing with quarterback injury problems too
- Packers O-Line Chaos Is Self-Inflicted And Hugely Problematic
Current
·
C2
·2026-11





