A healthcare provider is designing a new electronic health records (EHR) management system on Google Cloud. The system requires a relational database that supports full ACID transactions, standard SQL queries, and automated regional high availability across zones within a single GCP region. The application's performance requirement is modest, capped at 3,000 IOPS, and does not demand global multi-region write scalability. Which database architecture should the Cloud Architect recommend to meet these technical requirements while minimizing overall cost and operational complexity?
- Provision a Cloud SQL for PostgreSQL instance configured with High Availability (HA) enabled across two zones in the target region.Cevap
- BDeploy a multi-region Cloud Spanner instance to store the transactional health records with automatic synchronous replication.
- COrder a Google Cloud Transfer Appliance to continuously stream real-time transactional database updates to Cloud Storage buckets.
- DImplement a Cloud Bigtable cluster utilizing Customer-Supplied Encryption Keys (CSEK) to store the structured transactional records.
Cevap
Provisioning Cloud SQL for PostgreSQL with regional High Availability enabled across two zones is the optimal choice for single-region relational workloads requiring ACID transactions and standard SQL.
Cloud SQL for PostgreSQL provides a fully managed relational database supporting standard SQL and ACID transactions. Enabling regional High Availability (HA) across two availability zones satisfies the single-region availability requirement efficiently without incurring the substantially higher cost of global relational database engines.
Adım Adım Çözüm
Anahtar Kavram
Selecting Cloud SQL vs. Cloud Spanner based on regional scope and transactional requirements