An organization is deploying an enterprise application requiring a relational database on Google Cloud to handle financial transactions across three continents. The transaction volume requires predictable low latency (<10 ms reads and writes) globally, automatic horizontal scaling without manual sharding, and strong serializable consistency. As a Principal Cloud Architect, which database provisioning strategy should you select to meet these technical requirements while minimizing operational maintenance?
- Provision a Cloud Spanner instance configured with a multi-region instance configuration spanning the required geographical regions.Cevap
- BProvision a Cloud SQL for PostgreSQL instance with cross-region read replicas in each target continent and execute automated application failovers.
- CProvision a multi-node Compute Engine cluster running self-managed PostgreSQL with custom continuous replication and manual database sharding.
- DProvision a multi-region Cloud Bigtable cluster with multi-cluster routing enabled to support global write transactions.
Cevap
Provision a Cloud Spanner instance configured with a multi-region instance configuration.
Cloud Spanner is the fully managed enterprise database service on Google Cloud engineered specifically for multi-region transactional workloads requiring strong (external) consistency, high availability, and automatic horizontal scaling without manual sharding.
Adım Adım Çözüm
Anahtar Kavram
Selecting and provisioning globally consistent relational database services (Cloud Spanner vs Cloud SQL)