The Architecture Pressure Test
A design is only as good as its behavior under the stress vectors that will actually arrive: load, change, failure, scale, people, and time.
Architecture is what still works after the diagram meets reality. The diagram shows the happy path. The pressure test asks what happens when the day is not happy.
The stress vectors#
Picture the core of your system as a node, with forces pushing in from every direction. Name them honestly:
- Load — twice the traffic, on the worst possible day.
- Change — a requirement you were promised would never change, changing.
- Failure — a dependency you trusted returning errors, or worse, returning slowly.
- Scale — ten times the data, not ten percent more.
- People — the engineer who understood it leaving; a new one inheriting it cold.
- Time — the same system, unattended, eighteen months from now.
The test#
For each vector, ask one question: what breaks first, and how loudly? Good architecture fails loudly and locally — a clear error, a contained blast radius. Bad architecture fails quietly and globally — corrupted data, a silent backlog, a number that's been wrong for a month.
You do not get to choose whether the pressure arrives. You only get to choose whether you designed for it before it did.
How to use it#
Run a new design through all six vectors in a single sitting, before writing code. Most weak architectures are strong against the vector the author personally fears and blind to the other five. The point of the test is to make the blind spots speak up while they are still cheap to fix.