TIL: The Database Connection Pool Nightmare That Taught Me Scalability Lessons

When I first started building web applications, I thought scaling was all about writing efficient code and throwing more servers at the problem. Boy, was I wrong. My wake-up call came during a late-night deployment of what I confidently believed was a "high-performance" e-commerce platform. Within hours of going live, our site ground to a halt. After frantic debugging sessions, I discovered the culprit: our application was opening a new database connection for every single request without ever closing them properly. What made this even worse was that I had naively set the connection pool size to match our peak expected traffic, thinking "more connections = better performance." Instead, we quickly exhausted all available database connections, causing a cascading failure that brought down not just our app, but several other services sharing the same database.