Loading…
Compute, storage, networking, IAM, managed databases, serverless and cost.
Your team is about to deploy its first API to an Amazon EC2 instance (or an Azure Virtual Machine). What is a cloud virtual machine, and which parts of running it are still your job rather than the provider's?
A product manager hears that the new image-resize feature will run "on AWS Lambda" (or Azure Functions) and asks what that means. What is a serverless function, what makes it run, and how are you charged for it?
In cloud planning documents you keep seeing IaaS, PaaS and FaaS. What does each mean, and give one AWS or Azure compute service as an example of each.
Your team decides to ship its Node.js API as a container image and run it on Amazon ECS or Azure Container Apps. What is a container image, why ship the app that way, and where does the image live so the cloud service can run it?
A reviewer comments that your web app "must be stateless" before it can run as several instances behind a load balancer. What does stateless mean here, and what kind of data must not be kept on the instance itself?
Your HTTP API on AWS Lambda (or Azure Functions on the Consumption plan) usually answers in 80 ms, but the first request in the morning, and some requests during a sudden traffic spike, take two or three seconds. What is happening, and why do those particular requests pay the cost?