A logistics company is launching a new real-time package tracking API. During holiday seasons, the API experiences sudden, massive spikes in traffic (increasing by -fold within minutes) as users refresh their dashboards. The backend reads tracking data from an Amazon Aurora PostgreSQL database. The system must maintain low read latency during these spikes without impacting database write performance. Which strategy should the solutions architect recommend to handle these spikes at both the load balancer and database layers?
- ARely on the Application Load Balancer's (ALB) native automatic scaling to adjust to traffic surges, and deploy Amazon Aurora Replicas with Aurora Auto Scaling to distribute the query load.
- Request Application Load Balancer (ALB) pre-warming from AWS Support prior to the holiday season, and deploy Amazon Aurora Replicas with Aurora Auto Scaling to distribute the query load.Answer
- CRequest Application Load Balancer (ALB) pre-warming from AWS Support prior to the holiday season, and configure an Amazon RDS PostgreSQL Multi-AZ deployment to route read-only query traffic to the standby replica.
- DRely on the Application Load Balancer's (ALB) native automatic scaling to adjust to traffic surges, and configure an Amazon RDS PostgreSQL Multi-AZ deployment to route read-only query traffic to the standby replica.
Answer
Request Application Load Balancer (ALB) pre-warming from AWS Support prior to the holiday season, and deploy Amazon Aurora Replicas with Aurora Auto Scaling to distribute the query load.
The correct strategy requires pre-warming the ALB to handle the immediate -fold spike in traffic, combined with deploying Aurora Replicas and using Aurora Auto Scaling to handle the read query load without affecting the primary writer instance.
Step-by-Step Solution
Key Concept
Scaling Application Load Balancers for flash traffic and scaling relational database reads using Aurora Replicas.