What Is Serverless Computing?
Serverless computing lets developers run code without provisioning or managing servers directly — the cloud provider automatically handles scaling, and you'r...
Published November 19, 2026
Serverless computing lets you run code without managing servers: the cloud provider runs your functions on demand, scales them automatically and bills only for execution time. Examples: AWS Lambda, Google Cloud Functions, Cloudflare Workers.
The concept
Servers still exist, you just do not provision or patch them. A function runs in response to events (HTTP request, file upload, schedule) and stops when done.
Trade-offs: cold-start latency, execution time limits, vendor lock-in and harder local debugging.
Event-driven
Practical examples
AWS Lambda handler
export const handler = async (event) => ({
statusCode: 200,
body: JSON.stringify({ hello: event.queryStringParameters?.name ?? 'world' }),
})Cloudflare Worker
export default { fetch: () => new Response('Hello from the edge') }Cost model
Pay per request and GB-seconds; zero cost at zero trafficCommon mistakes
- Long-running jobs that exceed time limits.
- Ignoring cold starts for latency-sensitive paths.
- Storing state in the function instance.
Key takeaways
- No server management, pay per use.
- Great for spiky, event-driven work.
- Mind cold starts and limits.
FAQ
Serverless vs containers?
Serverless abstracts scaling entirely; containers give more control.
What is a cold start?
The delay when a new function instance spins up.