Every architecture review I have ever sat in eventually collides with the same wall, and it is never the budget. A stakeholder asks why the system cannot simply respond faster between two continents, and someone has to say, as kindly as possible, that the remaining delay is not in the code. It is in the universe. Physics signs exactly one service-level agreement, and in twenty years I have never seen a vendor renegotiate it.
- Light crosses a room in nanoseconds and the planet in noticeable fractions of a second. That gap is where distributed systems live.
- Below, race three runners between real cities: light in vacuum, light in fibre, and a packet on a realistic route.
- When the numbers land, you will know why your call home has a rhythm to it, and why engineers move data instead of arguing with Einstein.
The Law, in Engineering Units
Light in vacuum covers 299,792 kilometres each second, and nothing that carries information goes faster. That is not a benchmark to beat next hardware cycle; it is the structure of the universe, stated in engineering units. Inside optical fibre, light drops to roughly two-thirds of that, because glass is not vacuum. And a real packet never takes the great-circle path anyway: it follows cables that hug coastlines, land at exchange points, and zig where the geography zags. Race Lahore and Munich above, my call home, and read the lanes: the physics floor is a few tens of milliseconds, one way, before a single line of anyone's software has run.
Now put that number beside the ones your day is built from. A 60fps game redraws every 16.7 milliseconds: an ocean crossing cannot fit inside a single frame, ever. A human conversation starts to feel laggy somewhere past two hundred milliseconds of round trip, which is why intercontinental video calls have that faint walkie-talkie rhythm no app update will ever remove. The rhythm is not a bug. It is geography, billed at the speed of light.
What Engineers Do About a Law
You cannot negotiate with this limit, so the entire discipline of global systems is built on a single legal manoeuvre: if the data cannot travel faster, move the data closer before anyone asks for it. That is a CDN's whole job, and it is why the scaling ladder eventually forces every serious platform into multiple regions: not for fashion, but because the speed of light made a single home address physically incapable of feeling fast to the whole planet. It is also why the latency ladder puts a cross-continent round trip nearly a decade away from a cache hit, in stretched time. Every cache, every replica, every edge node on Earth is the same sentence spoken in infrastructure: we cannot beat light, so we stopped racing it.
I find this genuinely clarifying in reviews. Arguments about milliseconds split cleanly into two piles: the milliseconds someone's code is spending, which are negotiable, and the milliseconds the map is spending, which are not. Knowing which pile you are arguing about, before the meeting starts, is worth more than most benchmarks.
Physics signs exactly one SLA. Everything after that is negotiation with geography.
Its Place on the Map
On the Cabinet's map this exhibit rides the seam between Physics and Computer Science, and it earns that seat literally: a constant measured by physicists in the nineteenth century is now a line item in every serious architecture document of the twenty-first. Of everything in this room, this is the exhibit I have used most often in my actual job, usually in one sentence, usually to end a debate gently.
Before you go, race the two cities furthest apart in your own life. That number in the gold lane has been inside every call between them.