AWS, Azure & GCP · Cloud across providers
What is serverless computing?
Short answer
Serverless runs code or managed services without you provisioning servers; the platform handles scaling and patching, and you pay per request or execution time. It suits event-driven and bursty workloads with limits.
Serverless is an operating model more than a single product. Functions, managed queues, managed databases and API gateways can all be serverless. You do not choose or patch hosts, and capacity scales automatically with demand.
Characteristics
- Event-driven invocation from HTTP, queues, schedules, storage events or streams
- Automatic scaling, including scale to zero on some platforms
- Per-request or per-duration billing rather than paying for idle servers
- Stateless execution with external state in databases, caches or object storage
- Provider-managed runtime, patching and availability
export async function handler(event) {
const body = JSON.parse(event.body);
return {
statusCode: 200,
body: JSON.stringify({ orderId: body.orderId }),
};
}The trade-offs are execution time limits, memory and package size limits, cold starts, limited local disk, and concurrency quotas. Long-running batch jobs, custom kernels and latency-critical steady traffic often fit containers better.
Follow-ups you should expect
Interviewers use these to check whether the first answer was understanding or memorisation.
- 1What causes cold starts and how do you reduce them?
- 2How do you handle state in a serverless application?
- 3When does serverless become more expensive than containers?
- 4How do you debug a distributed serverless workflow?
Say it in the interview
Serverless means I do not provision or patch servers; the platform scales and bills per request or execution time. It fits event-driven, bursty and glue workloads, and state lives in external services. I watch the limits, cold starts and concurrency quotas, because they decide whether serverless is simpler or just hides the operational work.
Use this as a model, not a script. Saying it in your own words is what makes it survive follow-up pressure.
Related questions
Reading is step one
Now say it out loud.
Understanding an answer and delivering it under pressure are different skills. Rehearse this topic in a live AWS, Azure & GCP mock interview and get scored feedback on depth, clarity and confidence.