Writing
In-depth investigations of the systems and mechanisms behind software behaviour.
The Deep Stack follows engineering questions wherever the explanation leads: through application code, programming languages, runtimes, operating systems, hardware, networks, databases, and distributed systems.
Each article moves beyond an interface or symptom to explain the mechanism, test the explanation against evidence, and show what it means for engineering decisions.
Initial series
Systems under load
How performance emerges across application code, runtimes, operating systems, hardware, networks, databases, and infrastructure. Articles will examine capacity, contention, latency, overload, observability, and the methods used to investigate them.
Correctness beyond happy paths
How distributed business workflows preserve their guarantees through retries, partial failure, concurrency, and recovery. Articles will examine transactions, idempotency, queues, consistency, invariants, and failure handling.
These series provide a focused starting point.
Wider scope
Future investigations may examine reliability, security, operability, observability, resource use, architecture, and other properties of software systems. The subject can move through any layer of the stack when that is where the explanation leads.
How topics are chosen
A topic belongs in The Deep Stack when understanding it requires more than an API-level explanation and the answer can be supported by measurements, experiments, source code, documentation, standards, or research.
What to expect
Claims are supported with measurements, experiments, source code, documentation, or research. Each article connects the underlying mechanism to decisions engineers make when they design, debug, and operate software.