An online gaming platform is designing its architecture on Google Cloud for a single-region backend deployment. The system needs to support a relational user profile database that requires regional high availability but does not require multi-region global synchronization. Additionally, the platform runs a short daily batch analytics job that parses 50 GB of match logs stored in Cloud Storage. The architecture team needs to minimize baseline operational costs and avoid paying for idle compute resources during non-peak hours. Which TWO architectural decisions should you recommend to satisfy these requirements?
- Use Cloud SQL for PostgreSQL with regional High Availability (HA) for the user profile database.Answer
- BProvision a multi-region Cloud Spanner instance with high-priority processing units for the user profile database.
- Execute the daily log processing batch task using containerized Cloud Run jobs scheduled via Cloud Scheduler.Answer
- DDeploy a persistent Google Kubernetes Engine (GKE) Standard cluster running continuously to process the daily log batch job.
Answer
The optimal solution is to use Cloud SQL for PostgreSQL with regional High Availability for the database tier and execute the daily batch analytics job using scheduled Cloud Run jobs.
Cloud SQL with regional High Availability provides robust single-region failover and relational storage without the high baseline costs of Cloud Spanner. Cloud Run jobs provide a serverless execution environment that runs batch tasks to completion and automatically scales down to zero, ensuring costs are strictly proportional to execution time.
Step-by-Step Solution
Key Concept
Selecting right-sized database and serverless compute primitives to optimize cloud cost and operational overhead based on application scope.