Survive the viral launch

expert

Scenario & brief

Launch day: 15,000 rps, and the product cannot go down or crawl. You need 99.99% availability, p99 ≤ 110 ms, critical durability — and still come in under $2,200/mo. There is no slack; every tier must be tuned.

To pull this off: a CDN to carry static/edge load, an autoscaling Graviton origin across three AZs with enough ceiling for the peak, a healthy ElastiCache tier, and a Multi-AZ database with a read replica so the data tier also tolerates an AZ loss. Then squeeze cost with the right purchasing model. This is the full boss fight.

15,000 rps peakp99 ≤ 110ms99.99% availdurability: criticalbudget $2,200/mo

CloudFront

Networking

Enable CDN

System health

Erupting · SLA breach

/ 100

Score

SLA not met yet

Monthly cost

$4,904

Budget $2,200/mo · $2,704 over

Metrics

Capacity23

Availability30

Durability25

Cost efficiency0

Requirements

Peak capacity — 52000 rps compute · 3400 rps db (need ≥ 15000 rps)
p99 latency — ~134 ms (need ≤ 110 ms)
Availability — 99.00% (need ≥ 99.99%)
Durability — at risk (need redundancy + backups)
Budget — $4904/mo (need ≤ $2200/mo)

Advisor

The database is saturated at peak — add a cache to shed read load, or scale it up.
Compute runs in a single AZ — spread across ≥2 AZs (with ≥2 instances) to meet the availability target.
The database has no Multi-AZ standby or replica — a failure risks data loss. Enable Multi-AZ and backups.

Discussion

No comments yet. Be the first to start the discussion.

For learning purposes only. Costs and capacities are illustrative, not live AWS prices. Not affiliated with or endorsed by Amazon Web Services.