An online retail enterprise is migrating a stateless REST API service to Google Cloud. The workload experiences unpredictable traffic spikes during flash sale events but remains idle for extended periods overnight. The primary business goals are to minimize infrastructure costs by eliminating payment for idle compute capacity and to reduce operational overhead for an engineering team with no Kubernetes experience. Which architectural solution should a Cloud Architect recommend?
- Deploy the application using Cloud Run, configuring minimum instances to zero and leveraging pay-per-use request-based billing.Cevap
- BDeploy the application onto a Google Kubernetes Engine (GKE) Autopilot cluster using Horizontal Pod Autoscaling (HPA) to scale pods during traffic spikes.
- CProvision a Compute Engine Managed Instance Group (MIG) sized for peak traffic capacity and purchase a 3-year Committed Use Discount (CUD).
- DDeploy the stateless service alongside a multi-region Cloud Spanner instance with pre-provisioned processing units to handle request scaling.
Cevap
Deploy the application using Cloud Run, configuring minimum instances to zero and leveraging pay-per-use request-based billing.
Deploying the containerized application on Cloud Run directly satisfies all business and operational requirements. Because Cloud Run allows scaling down to zero instances, the enterprise incurs no compute costs during idle overnight periods. Furthermore, as a fully managed serverless product, it requires no underlying cluster administration or Kubernetes expertise.
Adım Adım Çözüm
Anahtar Kavram
Selecting serverless compute platforms (Cloud Run) over cluster-based or VM-based infrastructure to optimize costs for bursty, idle workloads while minimizing operational overhead.