A financial services organization is modernizing its transaction reconciliation architecture on Google Cloud. The architecture comprises two core workloads: (1) a stateless, containerized HTTP REST microservice that processes customer requests with highly variable traffic spikes and must scale down to zero instances when idle, and (2) a containerized batch job that processes end-of-day financial reconciliation files, running continuously for approximately 6 hours each night. The organization requires a solution that minimizes operational management overhead and eliminates compute infrastructure costs during idle periods. Which TWO compute platform selections should you recommend to meet these requirements?
- Deploy the stateless HTTP REST microservice to Cloud Run.Cevap
- Execute the 6-hour financial reconciliation batch job using Cloud Run Jobs.Cevap
- CDeploy the stateless HTTP REST microservice on a Google Kubernetes Engine (GKE) Autopilot cluster using Horizontal Pod Autoscaling (HPA).
- DProvision a Compute Engine Managed Instance Group (MIG) scaled via CPU utilization metrics to host the stateless microservice.
- EDeploy the financial reconciliation batch script to App Engine Standard Environment using background threads.
Cevap
Deploy the stateless HTTP REST microservice to Cloud Run, and execute the 6-hour financial reconciliation batch job using Cloud Run Jobs.
Cloud Run is the optimal platform for stateless containerized microservices requiring low management overhead and scale-to-zero capabilities. For containerized batch processes that run to completion over multiple hours (up to 24 hours), Cloud Run Jobs provides a fully managed execution environment that consumes resources only during active execution.
Adım Adım Çözüm
Anahtar Kavram
Selecting serverless compute platforms (Cloud Run services for stateless web APIs and Cloud Run Jobs for long-running batch tasks) to minimize operational overhead and idle costs.