memory, handed out in blocks
every app gets a private map
turns taken, 1000× a second
13 strangers pass it along
an agent is watching the logs
picks a machine that's free
narrowing, half at a time
01the tap
ina fingertip→outa signal
You touch
glass.
One tap. Seven layers now have to cooperate to answer it, and each one hands its work to the next. Follow the whole chain down.
02the order
ina signal→outa decision
Software
keeps order.
Hundreds of programs, one chip, a thousand handoffs a second. Something decides who goes next — and what happens when one of them fails.
03the transmission
ina decision→out1,500 bytes
The ask gets
wrapped and sent.
A parcel inside a parcel inside a parcel. Every layer is a note for whoever handles it next, and none of them may read what's inside.
04the route
ina name→out13 hops
Nobody knows
the whole way.
The name is traded for an address, then the parcel is passed between strangers who each know only who's next. Reliability is won or lost here.
05the room
ina request→outa queued job
It lands in a
room that hums.
Aisles of machines, cold air in and hot air out, and an agent reading the logs at 3 a.m. so nobody gets paged. This is the floor I work on.
06the processing
ina queued job→outone row
Data becomes
an answer.
A doorman, a cache, a pipeline, a sorted index that halves the search at every step — until billions of rows collapse into the one you asked for.
07the return
inone row→outlight
And then,
light again.
Back up all seven layers and painted onto glass inside sixteen milliseconds. My job is the middle five — the ones you never see fail.
layer 01 · surface
5 layers · 1.2 M lit dots
layer 02 · kernel
312 programs · 1 referee
layer 03 · transport
4 wrappers · 1500 bytes
layer 04 · network
name → address · 13 hops
layer 05 · platform
40,000 machines · 92 MW
layer 06 · data
4.1 B rows · 900 µs
layer 07 · return
round trip · 16 ms