Skip to content
Free since 2015. Built for the engineers who keep things running.

cat /articles/deterministic-simulation-testing.md

SRE & Incidents

Deterministic Simulation Testing

Unmesh Joshi explains how deterministic simulation testing replaces real clocks, networks, and storage with simulated ones so that distributed-system failures can be reproduced exactly. The walkthrough uses a quorum key-value store and the Java project Tickloom.

Martin Fowler17 Nov 2026 · 1 min read · summary

article --summary

The summary

This article walks through deterministic simulation testing, a way to make failures in distributed systems repeatable. The core problem is that partial failures happen alongside live traffic, so the same fault can play out differently each run and be hard to debug. The technique swaps real clocks, networks, and storage for simulated versions, all driven by a single-threaded execution loop. Because of this, the test can inject hard crashes as well as everyday slowdowns such as network and disk latency spikes, and every run can be replayed exactly the same way. The author applies the approach to a quorum key-value store as a running example, showing code from Tickloom, a Java implementation. Readers interested in testing distributed software will find it a practical look at how the method is built in practice.

Editorial note: This is a summary of an article first published by Martin Fowler. The full piece is on their site.

Reading now

Topic
SRE & Incidents
Source
Martin Fowler
Published
17 Nov 2026
Format
Curated summary

Have a take on this?

Write it up and submit it. It goes on the list once an editor approves it.

Submit an article

articles --latest

Latest articles

New from the blogs we follow and the community.

All articles

newsletter --weekly

DevOps Weekly, minus the noise.

The best reads, new jobs and upcoming events, in one email a week.