A production tier peaks at 6,000 rps and must hold 99.95% availability with critical durability and p99 ≤ 140 ms — on a tight $1,100/mo budget. Watch what pure Spot capacity being reclaimable in bulk does to that availability number.
All challenges
Purchasing strategy under an SLA
advancedScenario & brief
6,000 rps peakp99 ≤ 140ms99.95% availdurability: criticalbudget $1,100/mo
App Servers
Compute
6instances
System health
Erupting · SLA breach
28
/ 100
Score
SLA not met yet
Monthly cost
$2,054
Budget $1,100/mo · $954 over
Metrics
Capacity57
Availability30
Durability25
Cost efficiency8
Requirements
Peak capacity — 21600 rps compute · 3400 rps db (need ≥ 6000 rps) p99 latency — ~132 ms (need ≤ 140 ms) Availability — 99.00% (need ≥ 99.95%) Durability — at risk (need redundancy + backups) Budget — $2054/mo (need ≤ $1100/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
Sign in to join the 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.