Infrastructure

Serverless

You write functions and the cloud runs them on demand — no servers to provision or keep running.

'Serverless' doesn't mean there are no servers; it means you don't manage them. You upload a function, the platform spins up compute when a request arrives, runs it, and tears it down afterward — you pay per execution instead of for an always-on machine, and it scales from zero to thousands automatically. Analogy: renting a car by the minute versus owning one that sits in your garage. The tradeoffs to design around are cold starts, execution time limits, and statelessness — you can't keep things in memory between calls, so anything persistent has to live in a database.