Compute
App Engine
Fully managed PaaS — deploy code, not infrastructure
AWS equivalent
Elastic Beanstalk
AWS → GCP: Key Differences
- ▸
More opinionated than Beanstalk — Standard environment has strict runtime constraints but scales to zero instantly.
- ▸
Flexible environment runs Docker containers — similar to Beanstalk but GCP-managed.
- ▸
App Engine is older and most new GCP workloads use Cloud Run instead. But it's still widely deployed.
Key Concepts to Know
- 1
Standard environment: supported runtimes (Python, Java, Go, PHP, Ruby, Node.js). Scales to zero.
- 2
Flexible environment: any language via Docker. Runs on Compute Engine VMs. Minimum 1 instance.
- 3
Traffic splitting across versions — A/B testing or gradual rollouts built in.
- 4
App Engine is per-project: one App Engine app per GCP project.
- 5
Cron jobs and task queues built in (Cloud Scheduler and Cloud Tasks are the modern equivalents).
DCE Interview Tips
- ★
For migration conversations: if a customer has an App Engine app, they're locked to that project's region.
- ★
Modern recommendation: Cloud Run over App Engine for new workloads — more flexible, same serverless benefits.
- ★
App Engine Standard is still excellent for rapid deployments with no Docker knowledge required.
Common Gotchas
- !
App Engine Flexible minimum 1 instance costs money 24/7.
- !
You cannot change a project's App Engine region after creation.
- !
Standard environment has quotas on CPU time per request — not suitable for long-running processes.