Nine Things Have To Work
You click Buy. The page looks fine, the button responded, and your order never arrives. Between your finger and a warehouse sit nine separate layers of modern software — and each one fails with a completely different symptom. Guess how many first. Then break them one at a time and watch what the customer sees.
You click Buy on a website and an order appears in a warehouse. How many separate layers have to work perfectly for that one click to become an order?
What the customer sees
Nine layers, all green
Press Trace the click to follow one order all the way down and back. Then pick a layer and break it.
Layer
Pick a layer
Every layer in this stack exists because the one below it is too awkward to use directly. Click any of them to see what it does, who owns it, and what happens to your customer when it stops.
Text alternative — all nine layers, owners and failure symptoms
| Layer | What it does | Typical owner | What the customer sees when it breaks |
|---|
Nine layers, wired in series. Nine components that are each up 99.9% of the time multiply out to 99.1% — about 78 hours of customer-visible outage a year, from nine things that all look excellent on their own dashboard.
"The website is broken"
That sentence names a symptom and nine possible causes at once, so the call starts with twenty minutes of guessing. Describe what you saw instead — spinner, wrong price, vanished order, nothing at all — and you have narrowed nine layers to about two before anyone logs in.
Which layers stop being yours
Every SaaS purchase is a decision to stop owning some of these layers — usually the bottom five. That is almost always right, and it is not free: you keep the accountability for the whole chain while giving up the ability to fix most of it. The layer worth keeping is the one holding your actual business rules.
Nine layers, nine front doors
Each layer is a separate place to get in and a separate set of controls to evidence — patching belongs to the operating system, access belongs to the API, retention belongs to the database. A control that is strong at one layer proves nothing about the other eight, which is why "we're encrypted" is never an answer on its own.
Your teams are shaped like this diagram
Companies end up with a team per layer, and then every customer-visible problem crosses four of them. The handoffs in your org chart become the delays in your incidents — which is why teams that own a vertical slice from interface to database ship and recover faster than teams that own a horizontal one.
The layers exist because each one hides something awkward from the one above it: the database hides the disk, the operating system hides the hardware, the API hides the software, the interface hides all of it. That is the trade — every layer you add buys simplicity above it and adds a way to fail below it. Nine of them stand between a finger and a warehouse, they are wired in series, and the customer never sees a layer. They only ever see the symptom.
Keep going: Compute & Hardware zooms into the bottom layer — chip, rack, building, fleet. Nobody Owns the Whole Path turns this diagram on its side and shows how many separate companies one request crosses.