Level first-deploy — First DeployDrag components onto the canvas to build your architecture.
Start here: Connect EC2 → RDS (direct or via cache). Treat this like starter code: make one small architecture change, run it, then read the next coach step.
You've just joined a seed-stage startup. It's day one.
The CTO hands you a laptop and says: "We need the app live by Friday. It's Tuesday."
The stack is simple: a web server talking to a database. Your job is to wire it up and keep it running as real traffic arrives.
A small starting point is already on the canvas. Complete the missing pieces, run the simulation, and follow the coach as the system responds.
Connect EC2 to RDS. Keep your architecture alive as traffic ramps from 100 → 800 req/s.
Your app is stressed. Latency climbs. Users start noticing.
Requests are failing. Users see 503 errors. Score is dropping.
Database queries queue up. Everything downstream slows down.
If EC2 CPU spikes above 70%, click the node and upgrade the instance type. Bigger instance = more capacity.
"A single server has a limit. Every system does. This is yours."