Cloud Compute Options and Trade-offs Questions

Choosing among compute abstractions independent of provider: virtual machines, containers, managed container services, serverless functions, and bare metal. Covers the cost, control, cold-start, scaling, and operational trade-offs of each model; how to pick an instance family or hardware accelerator (general-purpose, compute-optimized, memory-optimized, GPU, TPU) and a purchasing model (on-demand, reserved, spot); and how workload characteristics (latency, statefulness, burstiness) drive the decision. Managed-versus-self-managed reasoning lives here.

HardTechnical
64 practiced

A product team asks you to choose between serverless and managed Kubernetes for a new platform with bursty traffic, long-lived WebSocket connections, and periodic heavy batch jobs. They are under deadline pressure and had informally been leaning toward serverless before looping you in. Present your recommendation with concrete trade-offs (cost, operational overhead, latency, developer productivity), and a rollout plan with success metrics.

MediumTechnical
70 practiced

You're an engineering manager deciding whether your team should adopt full Kubernetes or a simpler managed container service like AWS Fargate or Google App Engine. What criteria would you use to make that call, and how would your recommendation change for a team that's never operated a cluster before?

HardTechnical
53 practiced

For a legacy monolith currently running on VMs, compare a lift-and-shift to containers against rearchitecting to serverless microservices. For each approach, sketch a migration plan with phases, expected timelines, key risks, a testing strategy, and the metrics you'd use to decide which path to pursue.

That is every published Cloud Compute Options and Trade-offs question for Engineering Manager so far. Browse the other topics in this category, or practice this one interactively.