An e-commerce platform is migrating its core order processing service to Google Cloud. The workload consists of a stateless HTTP API that experiences unpredictable request bursts and a relational database with a 400 GB dataset requiring standard ACID transactions within a single region. The solution must guarantee 99.95% availability with automated zonal failover while requiring minimal operational management overhead. Which infrastructure architecture should you recommend?
- Deploy the HTTP API to Cloud Run configured across multiple zones and provision a High Availability (HA) Cloud SQL instance with a standby replica in a secondary zone within the same region.Cevap
- BDeploy the HTTP API to a regional Google Kubernetes Engine (GKE) cluster with node pools spanning three zones and provision a High Availability (HA) Cloud SQL instance.
- CDeploy the HTTP API to Cloud Run and provision a multi-region Cloud Spanner instance to host the relational database.
- DDeploy the HTTP API on Compute Engine Managed Instance Groups using fixed CPU-based autoscaling thresholds across zones and connect to an HA Cloud SQL instance via HA VPN.
Cevap
Deploy the HTTP API to Cloud Run configured across multiple zones and provision a High Availability (HA) Cloud SQL instance with a standby replica in a secondary zone within the same region.
Combining Cloud Run with a High Availability Cloud SQL instance provides a fully managed, serverless, high-availability architecture within a single region. Cloud Run automatically handles multi-zone request balancing and scaling for stateless containerized HTTP workloads, while HA Cloud SQL utilizes synchronous storage replication and automated failover to a standby zone, satisfying the 99.95% availability target with minimal operational overhead.
Adım Adım Çözüm
Anahtar Kavram
Designing High Availability Architectures for Stateless Compute and Relational Data on GCP