A global retail enterprise is building a lightweight, stateless microservice to handle peak spikes of HTTP inventory availability queries during high-volume promotional events. Traffic to this microservice exhibits extreme variability, surging from zero requests during off-peak hours to tens of thousands of HTTP requests per second during flash sales. The engineering team requires a containerized execution environment that automatically scales down to zero instances to minimize costs, requires zero underlying server or cluster management overhead, and charges strictly per millisecond of request processing time. Which Google Cloud compute platform should the Cloud Architect select?
- Deploy the containerized service to Cloud Run.Answer
- BDeploy the containerized service to a Google Kubernetes Engine (GKE) Autopilot cluster.
- CDeploy the service on a Compute Engine Managed Instance Group (MIG) configured with CPU-based autoscaling.
- DDeploy the service using App Engine Flexible Environment.
Answer
Deploying the microservice to Cloud Run satisfies all requirements for stateless execution, automatic scaling to zero, zero cluster management overhead, and request-based billing.
Cloud Run is designed specifically for stateless containerized workloads. It scales instances automatically up and down (including scaling down to zero when idle), eliminates infrastructure and cluster administration overhead, and charges only for compute resources consumed while processing requests.
Step-by-Step Solution
Key Concept
Compute Platform Selection for Stateless Bursty Microservices