An enterprise logistics provider is architecting a mission-critical fleet management service on Google Cloud within a single GCP region. The workload consists of a lightweight, stateless HTTP microservice that experiences fluctuating request volumes, and a relational database backend requiring multi-zone high availability with automatic failover to satisfy a strict regional Uptime SLA. The backend database does not require global distribution or horizontal write scaling. Which architectural design meets these technical and high availability requirements while minimizing operational overhead and unnecessary infrastructure costs?
- Deploy the microservice on Cloud Run integrated via a Serverless VPC Access connector to a regional Cloud SQL instance configured for High Availability (HA) across multiple zones.Cevap
- BDeploy the microservice on a regional Google Kubernetes Engine (GKE) cluster with node pools across three zones, and store relational data in a multi-region Cloud Spanner instance.
- CDeploy the microservice on Compute Engine virtual machines managed by a Regional Managed Instance Group (MIG), with load balancer health checks configured to directly query deep database endpoints to verify web node health.
- DDeploy the microservice on Cloud Run and connect to a single-zone Cloud SQL instance configured with automated daily snapshots to achieve cross-zone failover.
Cevap
Deploy the microservice on Cloud Run integrated via a Serverless VPC Access connector to a regional Cloud SQL instance configured for High Availability (HA) across multiple zones.
Combining Cloud Run with a regional Cloud SQL HA deployment directly satisfies the requirement for multi-zone high availability, automated failover, and scaling under fluctuating traffic while keeping operational overhead and costs minimal.
Adım Adım Çözüm
Anahtar Kavram
Designing High Availability for Regional Web Application Tiers
Tahmini Süre:1m 30s