Serverless
ELI5 — The Vibe Check
Serverless doesn't mean there are no servers — it means YOU don't have to think about servers. Someone else manages them, scales them, and patches them. You write functions or deploy apps and pay only when they're running. The servers exist; they're just not your problem.
Real Talk
Serverless is a cloud execution model where the provider dynamically manages resource allocation, scaling, and infrastructure. Developers deploy code as functions (FaaS) or use serverless platforms, paying only for actual usage. Examples: AWS Lambda, Vercel, Netlify Functions, Cloudflare Workers. Trade-offs include cold starts and vendor lock-in.
When You'll Hear This
"We went serverless to eliminate idle server costs." / "Serverless is great until you hit a cold start during a user-facing request."
Related Terms
BaaS (Backend as a Service)
BaaS is when someone provides you a ready-made backend so you can build your frontend without writing any server code.
Cloud Function
A cloud function is a piece of code you deploy to the cloud that runs when triggered — by an HTTP request, a file upload, a timer, or another event.
Cold Start
A cold start is the delay you get when a serverless function hasn't been used for a while and the cloud needs to spin up a fresh container to run it.
Edge Function
Edge functions run your code at the CDN edge — meaning close to the user, not in some faraway data center.
FaaS (Function as a Service)
FaaS is when you write a tiny function and deploy it to the cloud, and it only runs (and charges you) when someone calls it.
Lambda
AWS Lambda is where you upload a function and AWS runs it when something happens — an HTTP request, a file upload, a database change.