A developer hit a wall while building a static site with Node.js and PostgreSQL. Generating 70+ pages simultaneously triggered a connection pool explosion, causing frequent build failures. The core issue? Node.js's aggressive concurrency fires off all database queries at once, overwhelming standard connection limits.

Standard fixes failed. Increasing pool size didn't solve the creation rate. Manual connection handling made things worse.

Even Prisma's built-in pooling couldn't handle the build-time concurrency. The solution involved creating a query queue using a promise chain. During builds, queries execute serially, waiting for the previous one to finish.

At runtime, they run concurrently. This pattern uses `globalThis` to maintain state across module boundaries, which is a rare legitimate use for global state. The result: 100% build success and reliable performance for production sites.