Prisma Connection Pool Exhausted on Vercel

Your v0-generated Next.js application deployed on Vercel exhausts the database connection pool under moderate traffic. Each serverless function invocation creates new Prisma client instances that open their own database connections, and these connections are not shared across function invocations. As traffic increases, the database rapidly hits its maximum connection limit.

PostgreSQL databases on services like Supabase, Neon, or PlanetScale have connection limits ranging from 20 to 200 depending on the plan. With Vercel's serverless functions each maintaining their own connection pool, even modest traffic of 50 concurrent requests can exhaust all available database connections.

When the pool is exhausted, new requests queue up waiting for a connection, leading to timeouts and 500 errors that cascade across the entire application.