layman/terms
Going live

Serverless

sur · ver · less

In shortRunning code in the cloud without managing any servers yourself, paying only for the moments it actually runs.

Owning a car means insurance, servicing and parking, even when it sits unused. Taxis just turn up when you need them.

Owning a car means paying for it every day: insurance, servicing, parking. Even when it sits unused on the drive. Taxis are different. One turns up when you need it. You pay for that trip alone.

Serverless is taking taxis. You give a cloud company your code. It runs only when needed, you pay only for those moments and you never look after a server.

Why people like it

Where it fits best

Jobs that happen in bursts: resizing a photo when it’s uploaded, sending an email when someone signs up, answering requests for a website. This website uses a small serverless worker for word requests.

What it isn’t

It isn’t truly without servers. The cloud company still runs plenty of them. You just don’t see or manage them.

Where the comparison breaks down

A taxi takes a few minutes to arrive. Serverless code usually starts in well under a second, though the first run after a quiet spell can be a little slower.

How the words fit together

The cloud rents computers. Containers package apps to run on them. Serverless hides the computers entirely.

Good to know

There are still servers. You just never see them. The name means “no servers for you to manage”.

When you'll hear it

“It's a serverless function.” A small piece of code that runs on demand in the cloud, with no server to look after.

“We only pay per request.” We pay each time the code runs, not for a machine sitting idle.

“Cold start.” A short delay the first time it runs after a quiet spell, while the cloud gets it ready.

Say it in a meeting

“Would paying only for use be cheaper than servers that sit idle most of the day?”