A global healthcare diagnostic platform is designing its telemetry processing backend on Google Cloud to handle unpredictable spikes in stateless containerized workloads across two geographic regions. The platform must maintain a strict Service Level Agreement (SLA) of 99.999% availability with a Recovery Point Objective (RPO) of 0 and a Recovery Time Objective (RTO) of near-zero seconds for transactional data operations. The architecture must minimize operational management overhead while supporting multi-region synchronous replication. Which architecture meets these technical requirements?
- Deploy the stateless backend on Cloud Run across multiple regions integrated with a multi-region Cloud Spanner instance.Answer
- BDeploy the backend on Google Kubernetes Engine (GKE) Enterprise clusters across two regions backed by Cloud SQL for PostgreSQL with cross-region read replicas.
- CDeploy the backend on a Compute Engine Regional Managed Instance Group (MIG) backed by a Cloud Bigtable cluster with multi-cluster routing.
- DDeploy a dedicated GKE Standard regional cluster in each target region backed by a multi-region Cloud Spanner instance, configured with static CPU-based autoscaling.
Answer
Deploy the stateless backend on Cloud Run across multiple regions integrated with a multi-region Cloud Spanner instance.
The combination of Cloud Run across regions and multi-region Cloud Spanner fulfills all criteria. Cloud Run delivers serverless, zero-infrastructure scaling for stateless HTTP services. Cloud Spanner utilizes atomic clocks (TrueTime) and synchronous Paxos replication across regions to guarantee 99.999% availability, strong transactional consistency, and RPO = 0.
Step-by-Step Solution
Key Concept
Designing multi-region high availability architectures using Cloud Run and Cloud Spanner for zero RPO and 99.999% availability.