Cloud//serverless

>> 26.03.10 - let's build intuition for what serverless actually means. there is no server. there is no process listening on a port. when a request arrives, a function spins up, executes your handler, returns a response, and is destroyed. that's it. you define what should happen when something happens. cloud provider handles the rest.

26 · mar 10(day zero) let's build intuition for what serverless actually means. there is no server. there is no process listening on a port. when a request arrives, a function spins up, executes your handler, returns a response, and is destroyed. that's it. you define what should happen when something happens. cloud provider handles the rest.

Execution model where the cloud provider runs your code on demand, per request, without you managing servers. No process running 24/7. You deploy functions, the provider handles scaling, routing, and lifecycle. You pay per invocation, not per hour.

Cold starts are the main tradeoff -- first request after idle may be slower

Examples: AWS Lambda, Cloudflare Workers, Vercel Edge Functions, Google Cloud Functions

Contrast with traditional hosting where a Node/Express process runs continuously