A financial firm is deploying a regional transactional audit system in a single Google Cloud region (us-east4). The application requires ACID-compliant relational SQL storage with automatic zonal failover. The workload experiences standard traffic patterns, with total data storage expected to stay under 1 TB and throughput under 2,000 IOPS. The Chief Financial Officer requires an architecture that minimizes monthly compute and operational overhead while strictly maintaining regional high availability. Which database deployment strategy best fulfills these requirements?
- Deploy a Cloud SQL for PostgreSQL regional instance with High Availability (HA) enabled, utilizing a primary instance and a standby instance in a secondary zone.Cevap
- BDeploy a Cloud Spanner instance with multi-regional instance configuration to store the audit transactions.
- CDeploy a multi-zone Google Kubernetes Engine (GKE) cluster running a self-managed PostgreSQL StatefulSet with persistent disks.
- DPurchase 3-year Committed Use Discounts (CUDs) upfront for high-memory Compute Engine virtual machines configured as a custom PostgreSQL failover pair.
Cevap
Deploying a Cloud SQL for PostgreSQL regional instance with High Availability enabled best satisfies the business and cost requirements.
Cloud SQL with High Availability (HA) provides automatic failover to a standby instance in a secondary zone within the same region. For a single-region relational SQL workload under 1 TB, Cloud SQL offers fully managed backups, patches, and HA at the lowest total cost of ownership.
Adım Adım Çözüm
Anahtar Kavram
Selecting Cloud SQL over Cloud Spanner or self-managed GKE databases for single-region relational workloads to minimize cost and operational overhead.