Serverless for AWSs
AWS serverless is running code without managing servers. Lambda executes functions in response to events and bills by execution time, API Gateway exposes functions as HTTP APIs, and services such as SQS, SNS and EventBridge deliver events between components so applications scale automatically.
Stage: Compute · Part of the AWS roadmap · Last reviewed 19 November 2026
What to learn in Serverless
- Write and deploy a Lambda function with a handler
- Trigger a function from API Gateway, S3 or a queue
- Set memory, timeout and environment variables for a function
- Explain cold starts and ways to reduce their impact
- Connect services with SQS, SNS or EventBridge
Serverless interview questions
What is a Lambda cold start?
When Lambda has no warm execution environment ready, it must create one and load your code before running the handler, which adds latency to that invocation. Cold starts are more noticeable with large packages, some runtimes and VPC setups. Provisioned concurrency can keep environments warm.
When would you choose SQS between services?
SQS buffers messages in a queue so a producer is decoupled from a consumer. It absorbs traffic spikes, lets consumers process at their own pace and retries failed messages. Use it when work can be asynchronous and you want resilience against downstream slowness or failures.
Where Serverless fits in the AWS roadmap
Serverless belongs to the Compute stage (intermediate level), which takes about 25 hours. Run workloads.