Choosing Between Compute Engine, GKE, Cloud Run, and Cloud Functions

Overview and What You Will Learn

In this lab, you will deploy the same simple containerized application three different ways - on Compute Engine, then on Cloud Run - directly experiencing the operational overhead difference between full VM management and a fully managed serverless container platform.

Why This Matters in Production

A team building a simple internal reporting tool deploys it on a full Compute Engine VM they now have to patch, monitor, and manage forever, when Cloud Run would have handled the exact same workload with zero server management and automatic scale-to-zero when nobody's using it. The compute decision is the single most heavily weighted judgment call on the Associate Cloud Engineer exam, and the first real architecture decision most GCP newcomers face.

Core Principles

Each compute option trades control for operational simplicity, and the right choice depends entirely on what the workload actually needs.

Detailed Step-by-Step Practical Lab

1. Create a project and enable the necessary APIs:

2. Deploy a simple app on Compute Engine, taking on full responsibility for the OS:

3. Deploy the same conceptual app on Cloud Run instead, with zero OS management required:

4. Compare what each option required - the VM path needed ongoing OS management, while the Cloud Run path had Google handle it entirely:

5. Consider when the picture changes: if this reporting tool needed to become five interdependent containerized services - a web frontend, an API, a background worker, a cache, and a queue processor - all needing coordinated scaling and service discovery, that complexity is what justifies moving to GKE instead of either Compute Engine or Cloud Run alone.

6. Clean up:

Production Best Practices & Common Pitfalls

Common Mistake

Reaching for GKE by default because it feels like the more "serious" or scalable choice, then discovering the team is now managing cluster upgrades, node pool sizing, and Kubernetes networking complexity for a workload that was really just one simple containerized service Cloud Run would have handled with far less ongoing effort.

Tip

Start with Cloud Run for any standard stateless containerized web service unless a specific, concrete reason requires Compute Engine's full OS control or GKE's multi-service orchestration. Cloud Run's scale-to-zero and zero-OS-maintenance overhead outweigh the flexibility of a raw VM for the large majority of web workloads.

• Compute Engine is the right choice for a genuine, specific need - legacy software requiring a particular OS configuration, custom kernel modules, or workloads needing hardware-level access GKE and Cloud Run don't expose.
• Cloud Functions fits an even narrower niche than Cloud Run - a single-purpose, event-triggered piece of logic (like "resize this image when it's uploaded") rather than a full application with multiple routes and business logic, which Cloud Run handles more naturally.

Quick Reference & Troubleshooting Commands