An enterprise organization is architecting a public-facing API backend on Google Cloud to handle unpredictable burst traffic for a suite of stateless HTTP microservices. The business strategy mandates strict FinOps governance: infrastructure costs must scale strictly with incoming HTTP request volumes, scaling down to zero baseline cost during off-peak hours. Additionally, the organization has a lean Site Reliability Engineering (SRE) team that requires a fully managed environment to avoid node provisioning, OS patching, and Kubernetes cluster maintenance overhead. The services are packaged as standard OCI container images. Which compute platform architecture should a Cloud Architect recommend to satisfy these requirements?
- Deploy the containerized microservices directly to fully managed Cloud Run.Cevap
- BProvision a Google Kubernetes Engine (GKE) Autopilot cluster to deploy the microservice containers.
- CDeploy the containers to a Compute Engine regional Managed Instance Group (MIG) configured with CPU utilization autoscaling.
- DDeploy the microservices on Compute Engine Virtual Machines backed by 3-year Committed Use Discounts (CUDs) to baseline capacity.
Cevap
Deploying the containerized microservices directly to fully managed Cloud Run is the optimal architecture.
Deploying the microservices to fully managed Cloud Run fulfills all architectural constraints. Cloud Run provides a serverless platform that natively runs OCI container images, automatically scales up or down to zero instances based on incoming request traffic, eliminates baseline operational costs during off-peak idle hours, and completely removes cluster and OS maintenance burdens from the SRE team.
Adım Adım Çözüm
Anahtar Kavram
Selecting Serverless Container Compute (Cloud Run) vs. Managed Kubernetes (GKE) for Stateless Microservices
Tahmini Süre:2m 0s