Serverless

The name is a flat-out lie. There is absolutely still a server. There has to be. Your code has to run somewhere.

What "serverless" actually means is this: it's not your server, and it's not your problem.

Think about the light in a motel hallway versus the motion-sensor light in a parking garage. The hallway light burns all night whether anyone walks through or not, and somebody's paying for every one of those hours. The garage light sits dark, costing nothing, until you step in. Then it snaps on instantly, does its job, and clicks off the second you're gone. You pay for footsteps, not for the building.

That's the whole shift. You stopped renting a machine that runs around the clock and started paying by the moment your code actually does something.

The old way, so you can feel the difference. You rent a server (that always-on computer sitting in a warehouse) and it's yours now. Which sounds nice until you realize what "yours" means:

• It runs 24/7, and you pay for all 24, even the 3am hours when not one human is using your app.
• When it crashes, that's your pager going off.
• When it needs a security update, that's your Saturday.
• When a flood of traffic hits, you'd better have rented a bigger one in advance, or it falls over.

You're the landlord of a building that's lit up and heated all night for the occasional visitor.

The serverless way, you don't rent a building. You hand the provider (a company like Vercel, Cloudflare, or AWS) one small piece of code: one function that does one job. Things like:

• resize this image
• send this confirmation email
• check if this coupon is real

Then you walk away. When someone actually triggers that job, here's what happens:

1. A request comes in. "Someone just checked out. Send the receipt."

2. The provider grabs a machine out of a giant shared pool it keeps warm for everybody.

3. Your function runs on it, sends the receipt, and finishes.

4. The machine goes right back in the pool for the next person who needs one.

You never picked the machine. You never named it. You'll never know which one it was. And the meter only ran for the half-second your code was actually working.

So why should a non-coder care? Two reasons, both money and sanity.

• You pay for use, not for waiting. A side project that gets ten visitors a month can cost you basically nothing, because nothing's running while nobody's there. Compare that to renting a server that bills you every hour regardless. For most small or spiky things, this is the difference between a few cents and a real monthly bill.
• Traffic spikes stop being terrifying. Get featured somewhere and a thousand people show up at once? The provider just pulls a thousand machines out of the pool, runs your function a thousand times, and puts them all back. You didn't plan for it. You didn't upgrade anything. It just scaled, because it was never one machine to begin with.

There's one honest catch worth knowing, called a cold start. Remember the garage light snapping on the instant you walk in? It's almost that fast, but not quite. If your function hasn't run in a while, the provider has to grab a machine and wake it up first, which adds a beat of delay on that first request. Run it constantly and everything stays warm and snappy. Let it sit idle and the very next visitor waits an extra moment. Usually nobody notices. For something where every millisecond counts, people pay a little extra to keep the light always on.

That's the whole thing. You're not the landlord lighting an empty building all night anymore. The light's off until someone walks in, and you only pay for the footsteps.