An global logistics enterprise is architecting an event-driven supply chain routing service on Google Cloud. The workload handles stateless HTTP webhook payloads containing container tracking events, which scale rapidly from zero during burst peak hours to thousands of requests per second. The application requires standard HTTP/2 transport and zero infrastructure management overhead. Additionally, the development team requires built-in automatic scaling to zero when no events are processing to minimize operational costs. Which two GCP compute platform design choices, when combined, fulfill these requirements with the lowest operational complexity?
- Deploy the stateless web service as a fully managed Cloud Run containerized service.Cevap
- Configure Cloud Run concurrency settings to allow multiple simultaneous requests per container instance.Cevap
- CProvision an Autopilot Google Kubernetes Engine (GKE) cluster with a Horizontal Pod Autoscaler (HPA) configured for CPU utilization.
- DDeploy the workload across an Instance Group of Compute Engine Spot VMs behind a Network Load Balancer.
- EHost the application on App Engine Flexible Environment configured with manual scaling.
Cevap
Deploy the stateless web service as a fully managed Cloud Run service, and configure Cloud Run concurrency settings to process multiple simultaneous requests per container instance.
For stateless HTTP workloads that experience unpredictable burst traffic and require zero operational overhead alongside scale-to-zero capability, Cloud Run is the optimal Google Cloud platform. Enabling container concurrency further maximizes throughput and minimizes cost by allowing each running container instance to process multiple requests concurrently.
Adım Adım Çözüm
Anahtar Kavram
Selecting serverless compute platforms (Cloud Run) over container orchestrators (GKE) for stateless HTTP workloads requiring scale-to-zero and low operational overhead.