The Journey of a Ticket

How does my tap reach a kitchen a thousand miles away?

This film needs JavaScript and WebGL.

You tap Order in Caguas. The computer that takes your order is more than a thousand miles away. In less than a second, your ticket gets there, and back. Here's how.
First, your phone needs an address. It knows the name, pancarmen dot p r. But the network only understands numbers. So it asks the internet's phone book: the DNS.
The top of that phone book is thirteen named servers, copied in more than eighteen hundred places around the world. So the answer is always close by.
Your ticket is chopped into small envelopes called packets. Each one carries a from address and a to address, just like mail.
The envelopes are numbered, like registered mail. If one gets lost, the other side asks for it again, and everything is put back in order.
Packets hop from post office to post office. No post office knows the whole route. Each one only knows the best next stop.
Different companies own different roads. Where two of them meet and agree to swap traffic directly, that's called peering. Here in San Juan, networks meet at the island's own exchange, so local traffic doesn't have to fly to Miami and back.
To leave the island, packets ride on light, through glass cables on the ocean floor. Every one of those cables comes ashore at or near San Juan.
Before saying anything private, your phone checks the bakery's ID: a certificate, signed by someone both sides trust, like a notary. Then the two invent a secret code that only they know.
Only then does the ticket speak the shared language of the web, H T T P. Please create this order. And the answer races back the same way.
So where exactly is that kitchen? Not in Cayey. It lives in a place called the cloud. And the cloud is a very real building.