prisma-connection-pool-exhaustion

Serverless platforms like Vercel and AWS Lambda spawn isolated function instances that rapidly multiply Prisma client connections, exhausting the database connection pool. This Skill configures per-instance connection limits and external poolers to stabilize deployments.

To prevent connection exhaustion on Vercel, configure DATABASE_URL with connection_limit=1 and implement a global singleton PrismaClient. This ensures a single instance is reused across hot-reloads to prevent connection spikes.

The best way to pool Prisma connections for AWS Lambda and PostgreSQL is routing traffic through a dedicated pooler like PgBouncer or Prisma Accelerate. Combine this with a singleton PrismaClient to restrict per-instance connection limits.

You need PgBouncer or Prisma Accelerate for Netlify Functions using Prisma to manage concurrent requests effectively. These poolers sit between serverless functions and the database to limit and queue active connection requests.

Yes, you can apply this connection pooling configuration for MySQL backends in serverless deployments. The singleton PrismaClient pattern and connection_limit parameters work across PostgreSQL, MySQL, and other compatible databases.