HLDintermediatePremium

AWS Lambda HLD: How Serverless Runs Your Code Without a Server

How a serverless platform works inside: the invocation path, cold versus warm starts, the scheduler that reuses execution environments, concurrency-limited autoscaling, and where latency goes.

By fiveyearsdevJune 14, 20268 min read

"Serverless" doesn't mean there's no server — it means you never provision one. You hand the platform a function and an event source; it runs the function when events arrive, scales from zero to thousands of concurrent copies, and bills you per millisecond. The whole trick is on the platform's side: it keeps a fleet of execution environments, reuses a warm one when it can (fast), boots a fresh one when it must (the dreaded cold start), and caps how many run at once (concurrency). Get those three right and code scales itself. This is the inside of a Function-as-a-Service platform — Lambda, Clou…

What’s inside

Let's start nowhere near a computer

Where this exact shape shows up

Step 1 — Functional requirements (sentences first)

Step 2 — Non-functional requirements

Step 3 — The invocation path

Step 4 — The scheduler: reuse, create, or throttle

Step 5 — Concurrency and autoscaling

Step 6 — Trade-offs (each one keeping an NFR)

The complete implementation

Step 7 — Taming cold starts at scale

Step 8 — When a piece fails: designing for failure

The interview corner

Where to go from here

Read this one free

Sign in and your first premium article is on us — read AWS Lambda HLD: How Serverless Runs Your Code Without a Server free.

HLD