An enterprise SaaS platform hosts an internal reporting portal in a single Google Cloud region (). The portal executes relational SQL queries against a 1.5 TB database. Query traffic follows a predictable pattern, occurring strictly during weekday business hours (9:00 AM to 5:00 PM), with negligible usage overnight and on weekends. The primary business objective is to minimize total infrastructure costs while ensuring adequate database performance during business hours. Which architectural strategy best satisfies these requirements?
- AMigrate the database to Cloud Spanner and enable autoscaling to dynamically adjust compute nodes based on real-time query load.
- Maintain the workload on Cloud SQL for PostgreSQL and use Cloud Scheduler with Cloud Functions to dynamically scale up instance resources before business hours and scale down during off-peak periods.Answer
- CDeploy PostgreSQL on a Google Kubernetes Engine (GKE) cluster with StatefulSets and Horizontal Pod Autoscaling (HPA) to scale pods based on CPU consumption.
- DPurchase 3-year Committed Use Discounts (CUDs) for the maximum peak CPU and memory capacity to cover database provisioning continuously.
Answer
Maintain the workload on Cloud SQL for PostgreSQL and use Cloud Scheduler with Cloud Functions to dynamically scale up instance resources before business hours and scale down during off-peak periods.
Cloud SQL for PostgreSQL provides fully managed relational database functionality appropriate for single-region workloads. Because the traffic pattern is strictly tied to predictable business hours, leveraging automated scheduled scaling to scale up capacity before 9:00 AM and scale down after 5:00 PM minimizes operational spend without sacrificing performance when needed.
Step-by-Step Solution
Key Concept
Cost-optimized database selection and scheduled resource scaling for predictable workloads.
Estimated Time:1m 30s