Question

Difficulty: MediumDesigning Infrastructure for Technical Requirements and High Availability

An aerospace engineering enterprise is architecting a mission-critical global flight telematics platform on Google Cloud. The architecture requires a relational database that guarantees multi-region strong consistency, a zero Recovery Point Objective (RPO), and a near-zero Recovery Time Objective (RTO) during a regional outage. Additionally, the application tier consists of containerized stateless HTTP microservices that must automatically scale with traffic spikes while requiring minimal operational infrastructure management overhead. Which solution architecture satisfies these technical requirements and high availability objectives?

  1. Deploy the containerized stateless microservices on Cloud Run across multiple regions behind a Global External HTTP(S) Load Balancer, and store the relational telemetry data in a multi-region Cloud Spanner instance.Answer
  2. B
    Deploy the containerized stateless microservices on Cloud Run across multiple regions behind a Global External HTTP(S) Load Balancer, and store the relational telemetry data in a primary Cloud SQL for PostgreSQL instance with cross-region asynchronous read replicas.
  3. C
    Deploy regional Google Kubernetes Engine (GKE) clusters with custom node pools in each region to host the stateless microservices, paired with a regional Cloud SQL for PostgreSQL instance configured with High Availability (HA).
  4. D
    Deploy the stateless microservices on Compute Engine Managed Instance Groups (MIGs) in a single region, backed by a single-zone Cloud SQL instance with automated daily snapshots exported to Cloud Storage for disaster recovery.

Answer

Deploying the stateless containerized microservices to Cloud Run across multiple regions behind a Global External HTTP(S) Load Balancer combined with a multi-region Cloud Spanner database instance fulfills all high availability, operational, and consistency requirements.
The combination of Cloud Run and multi-region Cloud Spanner delivers an architecture that meets all specified operational and recovery constraints. Cloud Run provides serverless management for stateless HTTP containers, scaling dynamically with demand. Multi-region Cloud Spanner provides synchronous replication across regions using Paxos consensus, ensuring multi-region strong consistency, zero RPO, and automatic near-zero RTO failover.

Step-by-Step Solution

1
Evaluate the database tier requirements for consistency and availability
The requirements demand a relational database with multi-region strong consistency, RPO = 0, and RTO near zero.
Cloud Spanner uses TrueTime and synchronous multi-region replication to provide strong global transactional consistency and automatic failover with zero RPO.
2
Evaluate the compute tier requirements for operational overhead and workload type
The workload consists of containerized stateless HTTP microservices that require minimal management overhead and automatic scaling.
Cloud Run is a fully managed serverless container platform that automatically scales HTTP workloads from zero to peak demand without requiring infrastructure cluster management.
3
Synthesize the compute and database choices into a unified architecture
Combining Cloud Run with a Global External HTTP(S) Load Balancer and multi-region Cloud Spanner satisfies all technical constraints.
This end-to-end architecture guarantees global high availability, zero RPO regional failover, and serverless compute efficiency.

Key Concept

Multi-region high availability design using Cloud Run serverless compute and Cloud Spanner synchronous relational database storage.
Rate this question