Database bottlenecks under concurrency
- Challenge
- High-concurrency account and fund flows hit database saturation — latency spiked before the app layer looked unhealthy.
- How I Solved It
- Locust / Go load profiles (Locust WebUI), SQL / index review with engineering, and reproducible Docker DB environments for shared diagnosis.
- Result
- Stabilized critical paths under 500+ QPS pressure and shortened the feedback loop between QA and backend.