CLOUD / A CONCEPT NOTE
Serverless
run code without provisioning or managing servers
Overview · mechanism
pitfall · examples
01 / THE SHORT VERSION
The idea in a few sentences.
You upload a function (AWS Lambda, GCP Cloud Functions) or a container (Cloud Run), and the platform handles scaling, availability, and patching. You're charged per invocation and compute duration — zero cost when idle. The function is stateless and limited to a maximum execution timeout (usually 15 minutes for Lambda, 60 for Cloud Run).
02 / FOLLOW THE MECHANISM
How a lambda invocation flows
Trigger
an S3 upload, an API Gateway HTTP request, or an SQS message invokes the function.
Lambda service
finds or creates an execution environment (sandbox) with the configured memory and runtime.
Lambda runtime
downloads your code from S3, initializes the runtime (Python, Node, Go, etc.), and runs the handler outside the init phase.
Your handler
receives the event payload and context object (request ID, deadline, etc.). Returns a response or throws an error.
Platform
freezes the environment for reuse (warm start) or tears it down after inactivity (~5–15 minutes).
04 / COMMAND NOTES
Read the command, then the result.
Inspect the flags and arguments before trying an example. Snippets can need local setup, replacement values, or resources in your own environment.
invoke a Lambda synchronously
aws lambda invoke --function-name my-fn response.jsonlist all Lambda functions in the region
aws lambda list-functions05 / CHECK YOURSELF
Could you explain Serverless to a teammate?
Try it out loud in two sentences: what it is, and the one detail that changes the picture. If you stall, the gap is the part to reread.
Up next in Cloud architectureObject Storageunlimited, highly durable storage for any blob of data