prisma-connection-pool-exhaustion

What problem does it solve?

Solves database connection pool exhaustion in serverless Prisma deployments.

Core Features & Use Cases

• Connection pooling: Uses a pooler (PgBouncer/Prisma Accelerate) between serverless functions and the database to limit per-instance connections.
• Prisma client singleton: Implements a global singleton PrismaClient to avoid multiple client instances across hot-reloads.
• Deployment resilience: Applies to commonly used providers (Vercel, AWS Lambda, Netlify Functions) with PostgreSQL or MySQL backends.

Quick Start

• Configure DATABASE_URL with pooling parameters (connection_limit=1, pool_timeout, connect_timeout) or use a provider-specific pooled URL.
• Add a global PrismaClient singleton and ensure it is reused across requests.
• Consider a dedicated pooler like PgBouncer or Prisma Accelerate where supported.
• Deploy and monitor database connections to verify stability.