Server

By default, our laptop sleeps the second you shut the lid. A server is the opposite. Plugged in, online, awake, sitting in a rack in some warehouse in Virginia or Oregon, answering requests around the clock. Nobody's typing on it. No screen, no keyboard, no mouse. It just sits there and waits to be asked for things.

It's a computer with no bedtime.

Here's the part that makes it click. The word "server" is doing exactly what it sounds like: it serves. You're the customer. It's the waiter who never goes home.

So every time you type a URL and hit enter, this happens:

1. Your browser sends a request. "Hey, I want the page at this address."

2. Somewhere in the world, a server hears it, looks up what you asked for, and packages it up.

3. It sends that back to your browser, which paints it on your screen.

That entire round trip happens in the time it takes you to blink. And it happens millions of times a second, for millions of people, all day, forever.

To continue our restaurant analogy, this is where the metaphorical "kitchen" physically lives. The backend, the database, the business logic, all of it runs on a server somewhere. So when someone says "the server is down," they mean the kitchen turned off the lights. The waiter went home. Nothing's getting cooked tonight, and everyone standing at the door gets a blank stare.

A couple of things that surprise people once they see this:

• The "cloud" is not fluffy or magical. It's just someone else's servers. When you save a file to the cloud, you're putting it on a computer that probably belongs to Amazon or Google, sitting in a building you'll never visit. "The cloud" is marketing. It's racks of machines in a warehouse.
• One server can be many servers, and many servers can act like one. Big sites don't run on a single computer. They spread across hundreds of them so that if one dies, the others keep serving. That's why Instagram doesn't go fully dark every time one machine somewhere overheats.

Every website you've ever visited. Every app you've ever opened. A server answered the door.

Now, one twist worth knowing, because you'll hear it constantly. A lot of apps now run "serverless." That name is a little bit of a lie. There's still a server, you just don't have to own it, name it, or babysit it. A company like Vercel or Cloudflare keeps a giant pool of machines awake for everybody, and your app borrows one for the half-second it's needed, then lets it go.

No single computer with your name on it that you have to keep alive at 3am. It's the difference between owning a car and calling an Uber. The car still exists. You're just not the one parking or dealing with the headaches of owning.

We'll unpack serverless properly on another day. For now, the whole idea fits in one line:

Your laptop sleeps. A server doesn't.