An enterprise development team is deploying a stateless REST microservice packaged as a Docker container to Google Cloud. The workload experiences unpredictable traffic spikes followed by extended idle periods. The team requires zero infrastructure management overhead and rapid auto-scaling to zero instances when idle. Which TWO options represent the recommended design choices for this application?
- Deploy the containerized service to fully managed Cloud Run to handle request-based scaling and zero-instance idle scale-down.Cevap
- Configure concurrency settings on Cloud Run so each container instance processes multiple simultaneous requests.Cevap
- CDeploy the microservice onto a dedicated Google Kubernetes Engine (GKE) Standard cluster with a multi-zone node pool.
- DDeploy the microservice on Compute Engine Managed Instance Groups (MIGs) with scaling policy based strictly on host CPU utilization.
- EPurchase 3-year Committed Use Discounts (CUDs) for baseline compute capacity to lower costs for the microservice.
Cevap
Deploying the microservice to fully managed Cloud Run and configuring container concurrency settings.
Deploying the application to fully managed Cloud Run provides a serverless environment that automatically scales up with HTTP traffic and down to zero instances when idle. Configuring container concurrency allows each instance to handle multiple simultaneous requests efficiently, lowering overall operational costs and management overhead.
Adım Adım Çözüm
Anahtar Kavram
Selecting serverless container platforms (Cloud Run) and optimizing scaling configuration for stateless HTTP microservices.