Serverless
Definition & meaning
Definition
Serverless is a cloud computing execution model where the cloud provider dynamically manages the allocation and provisioning of servers. Developers write and deploy code as functions that run on-demand without managing infrastructure, scaling, or server maintenance. Despite the name, servers still exist — developers simply do not interact with them directly. AWS Lambda, Vercel Functions, and Supabase Edge Functions are common serverless platforms.
How It Works
Serverless computing is a cloud execution model where the cloud provider dynamically manages server allocation and scaling. Developers write individual functions that are triggered by events — HTTP requests, database changes, file uploads, scheduled timers, or message queue items. The cloud provider provisions a container (or microVM), loads your function code, executes it, returns the result, and then either freezes the container for reuse (warm start) or discards it. You are billed per invocation and per millisecond of execution time, with zero cost when the function is idle. The "serverless" name is a misnomer — servers still exist, but developers never provision, patch, or manage them. Modern serverless platforms support multiple runtimes (Node.js, Python, Go, Rust) and offer generous free tiers. Cold starts — the latency penalty when a new container must be initialized — remain the primary technical concern, ranging from 100ms for optimized Node.js functions to several seconds for Java. Provisioned concurrency and edge runtimes mitigate this.
Why It Matters
Serverless fundamentally changes the economics of running backend code. Traditional servers cost money 24/7 whether they serve one request or one million. Serverless scales to zero: if nobody calls your function, you pay nothing. It also scales infinitely upward — the provider handles thousands of concurrent invocations without any capacity planning. This makes serverless ideal for unpredictable traffic patterns, webhook handlers, background jobs, and APIs with variable load. Operational burden drops dramatically: no OS patching, no security updates, no capacity monitoring, no auto-scaling configuration. The team focuses entirely on business logic. We use serverless functions for API endpoints, image processing, email sending, and scheduled tasks — anything that doesn't require persistent connections or long-running processes.
Real-World Examples
AWS Lambda is the market leader with over 60% serverless market share, supporting 15-second to 15-minute execution windows. Vercel Functions and Netlify Functions provide serverless backends integrated with front-end deployment platforms. Cloudflare Workers offer a unique V8 isolate-based serverless runtime with sub-millisecond cold starts. Supabase Edge Functions run Deno-based serverless code. AWS Step Functions orchestrate multiple Lambda functions into workflows. A typical pattern: a Next.js API route deployed as a Vercel Function handles form submissions, validates input with Zod, writes to a Supabase database, sends a confirmation email via Resend, and returns a response — all without managing a single server. SST (Serverless Stack) and the Serverless Framework simplify AWS Lambda deployment and infrastructure management.