Crank the load on QuickMove and watch which layer saturates first — app CPU, DB connections, cache or queue. Diagnose before you scale: the #1 architect skill.
QuickMove is melting down at peak. Before you spend money scaling, read the symptom, guess the bottleneck, then run the load test and see which layer actually saturates first.
Symptom: App CPU looks fine, but bookings hang and logs show "connection pool exhausted."
800 req/s
Your diagnosis — which layer gives out first?
What just happened
▹Scaling starts with diagnosis, not tools. The same traffic saturates a different layer depending on which one is weakest — you can't fix what you haven't measured.
▹App CPU, DB connections, cache throughput and queue workers each have their own ceiling. The bottleneck is whichever hits 100% first; everything behind it just waits.
▹Adding app instances when the database is the bottleneck makes things worse — more instances open more connections to the layer that's already maxed.