prisma-connection-pool-exhaustion

What problem does it solve?

Serverless deployments spawn new Prisma clients per cold start, which opens several database connections and can exhaust the database's connection pool, causing timeouts and degraded performance.

Core Features & Use Cases

• Connection pooling with PgBouncer or Prisma Accelerate to cap concurrent connections.
• Provider-specific guidance for managed databases (Supabase, Neon) and how to enable pooling.
• PrismaClient singleton pattern to avoid creating new clients on every invocation.

Quick Start

• Update your DATABASE_URL to use a pooled connection string when supported (e.g., Supabase: postgresql://...:6543/...?pgbouncer=true).
• Limit connections in Prisma by configuring the datasource and optional URL parameters, e.g., append ?connection_limit=1 to the DATABASE_URL.
• Implement a PrismaClient singleton in your codebase (development and production) to survive hot reloads and cold starts.
• Verify with a load test and monitor database connections to ensure they stay within limits.