An online retail enterprise is preparing for an upcoming annual mega-sale expected to drive a projected surge in peak user traffic over a 48-hour window. Their primary application architecture consists of a stateless HTTP API tier deployed on Compute Engine Managed Instance Groups (MIGs) and a Cloud SQL PostgreSQL backend database. During previous smaller sales, sudden traffic spikes caused temporary latency spikes because MIG reactive autoscaling took several minutes to spin up new virtual machine instances, and the Cloud SQL backend suffered from connection exhaustion. Furthermore, the architecture team needs to ensure infrastructure scaling will not fail due to cloud platform limitations during the event. Which capacity planning and workload scaling optimization strategy should the Cloud Architect recommend?
- Audit existing project quotas and request regional Compute Engine CPU and IP quota increases well in advance, enable predictive autoscaling or schedule scheduled autoscaling scaling for the MIGs, and introduce connection pooling alongside database read replicas for Cloud SQL.Cevap
- BConfigure standard reactive CPU-utilization autoscaling on the Compute Engine MIGs with maximum instance limits set to scale out dynamically as requests arrive, relying on automated GCP dynamic quota allocation during the event.
- CRe-architect the stateless web application tier into a multi-region GKE Enterprise cluster using Autopilot mode to replace the Compute Engine MIGs, relying on GKE cluster management to resolve regional compute quota constraints automatically.
- DMigrate the Cloud SQL PostgreSQL database to a multi-region Cloud Spanner instance to automatically eliminate connection pooling limits and solve compute instance autoscaling bottlenecks on the frontend tier.