Compute for Google Clouds
Google Cloud compute covers the services that run your code: Compute Engine for virtual machines you manage yourself, and Cloud Run for containers that scale automatically and can drop to zero when idle. Choosing between them is a core design decision, trading control and fixed capacity against simplicity and per-request billing.
Stage: Compute · Part of the Google Cloud roadmap · Last reviewed 19 November 2026
What to learn in Compute
- Create a Compute Engine VM and connect to it with SSH
- Pick a machine type and boot disk that match a workload
- Deploy a container image to Cloud Run and read its public URL
- Set concurrency, memory and maximum instances on a Cloud Run service
- Decide when a VM is better than a serverless container
Compute interview questions
When would you choose Cloud Run over Compute Engine?
Choose Cloud Run for stateless HTTP services packaged as containers, where you want autoscaling, no server patching and billing based on use. Choose Compute Engine when you need full OS control, custom kernels, long-running stateful processes, GPUs attached to specific machines or software that cannot run in a container.
What is a managed instance group in Compute Engine?
A managed instance group is a set of identical VMs created from an instance template. It supports autoscaling, health-check based auto-healing and rolling updates, so a failed machine is replaced automatically and a load balancer can spread traffic across the group.
Where Compute fits in the Google Cloud roadmap
Compute belongs to the Compute stage (intermediate level). Run apps.
Other units in this stage
Back to the full Google Cloud roadmap