Question

Difficulty: HardDesigning Infrastructure for Technical Requirements and High Availability

A digital media enterprise is architecting a new real-time content recommendation service on Google Cloud. The service processes lightweight, stateless HTTP REST requests that experience erratic traffic patterns and must scale down to zero instances during off-peak hours to minimize operational overhead and baseline compute costs. Additionally, the service must reliably connect to an on-premises media archive with a continuous bandwidth requirement of 15 Gbps15\text{ Gbps} and a 99.99%99.99\% high availability SLA. Which architecture should you deploy to meet these technical and availability requirements?

  1. Deploy the application on Cloud Run integrated with a Serverless VPC Access connector, and establish Dedicated Interconnect with 99.99% availability using dual interconnect attachments across two distinct metro locations.Answer
  2. B
    Deploy the application on a regional Google Kubernetes Engine (GKE) cluster with autoscaling node pools, and establish an HA VPN gateway with dual active-active IPsec tunnels to the on-premises network.
  3. C
    Deploy the application on Cloud Run in a service VPC, and use VPC Network Peering to route traffic through a central hub VPC that connects to on-premises via a single Dedicated Interconnect link.
  4. D
    Deploy the application back-end using Cloud Spanner instances across three zones, and configure Cloud VPN over the public internet to synchronize on-premises assets.

Answer

Deploy the application on Cloud Run integrated with a Serverless VPC Access connector, and establish Dedicated Interconnect with 99.99% availability using dual interconnect attachments across two distinct metro locations.
Cloud Run is the ideal serverless compute platform for stateless microservices that require scaling down to zero during idle periods. Combining Cloud Run with a Serverless VPC Access connector allows compute instances to reach internal VPC resources. To meet the 15 Gbps bandwidth demand and 99.99% SLA requirement, Dedicated Interconnect with dual connections across two distinct metro locations is the required Google Cloud reference architecture.

Step-by-Step Solution

1
Evaluate compute options for stateless HTTP microservices requiring zero-scaling.
Cloud Run is the optimal platform because it natively scales down to zero instances when traffic drops to zero, avoiding baseline cluster management overhead associated with GKE.
Choosing GKE for simple stateless microservices introduces unneeded administrative complexity and persistent node costs.
2
Analyze hybrid network connectivity throughput and availability SLA requirements.
Sustained bandwidth of 15 Gbps exceeds HA VPN tunnel limits (~3 Gbps per tunnel), necessitating Dedicated Interconnect.
Dedicated Interconnect supports 10 Gbps or 100 Gbps physical circuits.
3
Formulate 99.99% SLA topology for Dedicated Interconnect.
Configure dual interconnect attachments connected to redundant Cloud Routers across two separate metro locations (edge availability domains).
Google Cloud requires dual metro connections to grant a 99.99% availability SLA for Dedicated Interconnect.

Key Concept

Designing High-Availability Hybrid Architectures with Serverless Compute and Dedicated Interconnect
Rate this question