Diagram
A decision tree that starts with a containerized workload and branches on statefulness, Kubernetes needs, and traffic patterns, leading to GKE for stateful or complex workloads with pay-per-cluster pricing and Cloud Run for stateless, variable workloads with pay-per-use pricing.
Matching the Service to Business Requirements
Matching the service to business requirements means choosing control when the workload needs customization and choosing simplicity when the workload needs speed and efficiency. GKE fits complex microservices, stateful inventory or data services, and workloads that need custom storage, networking, or resource allocation. Cloud Run fits stateless web front ends, mobile back ends, APIs, and periodic batch work where automatic scaling and paying only during use improve agility and resource efficiency:
| Service | Control and management | Application types | Pricing |
|---|---|---|---|
| GKE | Team manages clusters, including nodes, networking, scaling, and upgrades, with full customization | Stateless and stateful apps, including complex microservices with specific resource needs | Pay-per-cluster per hour |
| Cloud Run | Google manages infrastructure; team supplies code or image with no cluster to manage | Stateless, request-driven or event-driven web services, APIs, and batch jobs | Pay-per-use, rounded to nearest 100 milliseconds |
Domain 5 of 5
27 practice questions
Practice this DomainLast updated