An enterprise logistics company is designing a new HTTP microservice to process real-time package status updates submitted by driver mobile applications. The workload is completely stateless, packaged as a standard container image, and experiences extreme traffic variability ranging from zero requests overnight to tens of thousands of requests per second during peak hours. The lead architect wants to minimize operational management overhead and eliminate baseline infrastructure costs when no requests are being processed. Which Google Cloud compute platform should be selected for this workload?
- Deploy the container container image to Cloud Run.Cevap
- BProvision a Google Kubernetes Engine (GKE) Autopilot cluster with Horizontal Pod Autoscaler.
- CDeploy to a Compute Engine Managed Instance Group (MIG) autoscaling strictly on CPU utilization.
- DProvision persistent Compute Engine Virtual Machines reserved with 3-year Committed Use Discounts (CUDs).
Cevap
Deploying the container image to Cloud Run is the optimal architectural choice because it provides fully managed serverless execution for stateless HTTP workloads, scales automatically from zero to match request volume spikes, and incurs no compute costs during idle periods.
Cloud Run is specifically designed for containerized, stateless HTTP services that require fast automatic scaling. It manages all underlying infrastructure, handles request-based autoscaling dynamically from zero to thousands of instances, and charges only for compute resources consumed while processing requests.
Adım Adım Çözüm
Anahtar Kavram
Compute Platform Selection for Stateless Serverless Workloads
Tahmini Süre:1m 30s