A regional European gaming studio is designing the persistent database backend for an online multiplayer game's player profile and inventory management system. The database must run in a single Google Cloud region (europe-west3), support strict ACID transactional consistency, provide automated regional failover across multiple availability zones, and handle up to 15,000 IOPS during peak events. The team wants to avoid unnecessary architectural complexity and operational cost. Which storage and database architecture should you recommend to meet these requirements?
- Deploy a Cloud SQL for PostgreSQL instance with High Availability (HA) enabled across primary and standby zones within the region.Answer
- BProvision a multi-region Cloud Spanner instance with global replication to handle all transactional inventory operations.
- CUse a Google Cloud Transfer Appliance cluster connected to Cloud Storage to handle real-time transactional reads and writes.
- DConfigure a Cloud Bigtable cluster utilizing Customer-Supplied Encryption Keys (CSEK) to maintain strict transactional consistency across player profiles.
Answer
The recommended solution is deploying a Cloud SQL for PostgreSQL instance configured for High Availability (HA) within the single target region.
Deploying Cloud SQL for PostgreSQL with High Availability (HA) is the optimal choice. Cloud SQL provides native relational database capabilities with ACID compliance, and its HA option automatically replicates data synchronously to a standby instance in a secondary zone within the same region (europe-west3), ensuring quick failover while keeping costs and operational overhead aligned with single-region requirements.
Step-by-Step Solution
Key Concept
Selecting Cloud SQL versus Cloud Spanner for regional relational database workloads.