A smart grid energy utility is designing a backend solution on Google Cloud to ingest and process daily energy readings from millions of smart meters within a single geographic region. The application requires ACID-compliant relational data storage for daily billing reconciliation. Traffic patterns show predictable daytime peak activity followed by minimal volume overnight. The primary business requirement is to minimize total cost of ownership (TCO) and operational maintenance effort while maintaining single-region high availability. Which architecture should you recommend?
- Deploy the HTTP ingestion API on Cloud Run and store the billing transactional data in Cloud SQL for PostgreSQL configured with High Availability (HA).Cevap
- BDeploy the HTTP ingestion API on Cloud Run and store the billing transactional data in a multi-region Cloud Spanner instance.
- CDeploy a multi-zone Google Kubernetes Engine (GKE) Standard cluster to run the HTTP ingestion API containers and store the billing transactional data in Cloud SQL for PostgreSQL.
- DDeploy the HTTP ingestion API across Compute Engine Virtual Machines using 3-year Committed Use Discounts (CUDs) and store the billing transactional data in Cloud SQL for PostgreSQL.
Cevap
Deploying the HTTP ingestion service on Cloud Run combined with Cloud SQL for PostgreSQL configured for High Availability delivers the lowest cost of ownership and lowest operational overhead while meeting all ACID compliance and single-region availability requirements.
The combination of Cloud Run and Cloud SQL for PostgreSQL provides the optimal balance of operational simplicity and cost efficiency. Cloud Run handles the variable HTTP traffic by scaling down to zero during off-peak hours to eliminate idle compute spend. Cloud SQL delivers full ACID relational compliance for billing records within a single region without the premium baseline costs of multi-region database options.
Adım Adım Çözüm
Anahtar Kavram
Selecting cost-effective compute and database services aligned with regional bounds and variable workload scaling profiles.
Tahmini Süre:1m 30s