A company is migrating on-premises workloads to Google Cloud. They have a critical application that requires consistent low-latency access to a database, with read replicas in multiple regions for disaster recovery. The application is expected to grow by 10x over the next year. Which database service and configuration should the architect choose to meet these requirements?
Trap 1: Use Cloud Bigtable with multi-region replication
Bigtable is a NoSQL wide-column database optimized for analytical workloads, not transactional consistency.
Trap 2: Use Cloud SQL for PostgreSQL with cross-region read replicas
Cross-region replicas are asynchronous, not strongly consistent, and may not meet latency requirements.
Trap 3: Use Firestore in native mode with multi-region location
Firestore Native mode is eventually consistent, not strongly consistent across regions.
- A
Use Cloud Bigtable with multi-region replication
Why wrong: Bigtable is a NoSQL wide-column database optimized for analytical workloads, not transactional consistency.
- B
Use Cloud SQL for PostgreSQL with cross-region read replicas
Why wrong: Cross-region replicas are asynchronous, not strongly consistent, and may not meet latency requirements.
- C
Use Cloud Spanner with multi-region configuration
Cloud Spanner offers global strong consistency, automatic replication, and horizontal scalability.
- D
Use Firestore in native mode with multi-region location
Why wrong: Firestore Native mode is eventually consistent, not strongly consistent across regions.