Question

Difficulty: MediumDesigning Infrastructure for Technical Requirements and High Availability

A regional e-commerce platform is re-architecting its containerized order reservation backend on Google Cloud. The application consists of stateless HTTP services handling unpredictable traffic spikes during promotional events. The solution must run within a single GCP region while ensuring high availability across multiple zones, automatic scaling from zero, and minimal cluster management overhead. The underlying relational database requires ACID transactional integrity within the region and automatic standby failover. Which architecture meets these technical and high availability requirements with the lowest operational complexity?

  1. Deploy the stateless microservices on Cloud Run connected via Serverless VPC Access to a regional Cloud SQL instance configured with High Availability (HA).Answer
  2. B
    Deploy the stateless microservices on a multi-zone Standard Google Kubernetes Engine (GKE) cluster and connect to a regional Cloud SQL instance configured with High Availability (HA).
  3. C
    Deploy the stateless microservices on Cloud Run connected via Serverless VPC Access to a multi-region Cloud Spanner instance.
  4. D
    Deploy the stateless microservices on Cloud Run and configure HTTPS Load Balancer health checks to execute direct SELECT queries on the backend database.

Answer

Deploying the stateless microservices on Cloud Run coupled with Serverless VPC Access to a regional Cloud SQL for PostgreSQL/MySQL HA instance satisfies high availability, auto-scaling, and single-region transactional requirements while minimizing operational overhead.
The combination of Cloud Run and Cloud SQL in High Availability (HA) mode perfectly satisfies all technical requirements. Cloud Run provides serverless container execution that scales seamlessly with traffic spikes while eliminating cluster maintenance overhead. Cloud SQL HA uses synchronous replication across two zones within the region to deliver automatic failover and high availability for relational workloads.

Step-by-Step Solution

1
Evaluate compute tier requirements against operational overhead constraints.
Cloud Run handles stateless HTTP containers with automatic scaling (including scale-to-zero) and requires zero infrastructure management, making it superior to GKE for low operational overhead.
The requirement explicitly asks to minimize cluster management and operational complexity.
2
Evaluate database tier requirements for single-region ACID transactional compliance and high availability.
Cloud SQL configured in High Availability (HA) mode provides a primary instance in one zone and a synchronous standby instance in a second zone within the same region.
Cloud SQL HA meets regional RPO=0 synchronous replication and fast failover needs without the cost and operational complexity of globally distributed databases like Cloud Spanner.
3
Determine secure private networking between serverless compute and database resources.
Serverless VPC Access connector allows Cloud Run instances to route traffic privately into the VPC network to reach internal Cloud SQL IP addresses.
Direct private IP communication protects database endpoints without exposing public IP addresses.

Key Concept

Designing serverless high availability architectures using Cloud Run and Cloud SQL HA
Rate this question