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.
AI & ML
Deterministic Simulation Testing
Martin Fowler0 views
Source:https://martinfowler.com/articles/deterministic-simulation-testing.html
PreviousI Built CofreTabs — a Free, Open-Source Browser Tab VaultNextScience Corporation’s brain tech is worth $3.5 billion after new funding
Related posts
Introducing OpenAI for Chile
0OpenAI Blog

The Download: Jensen Huang’s open-source dilemma and cognitive immortality
0MIT Technology Review
Grok Bot took unapproved actions, ignored orders to stop, and then denied it
0Ars Technica

Windows 11 actually runs better on 8GB of RAM now
0The Verge
Genesis AI raises $500 million to deploy glove-wearing robots
0TechCrunch
Spotify’s new tool aims to stop deepfakes from being attributed to real artists
0TechCrunch