prisma-connection-pool-exhaustion

To fix Prisma connection pool exhaustion in serverless environments, implement connection pooling infrastructure like PgBouncer or Prisma Accelerate, and use a singleton PrismaClient to prevent connection leaks during high concurrency.

The best way to configure a Prisma client for AWS Lambda or Vercel is to instantiate a singleton PrismaClient globally. This prevents per-request client creation, significantly reducing cold-start connection spikes and avoiding pool exhaustion.

Your Prisma serverless app exceeds the PostgreSQL connection limit under load because each serverless function instance creates new Prisma clients. Introducing a pooler like PgBouncer caps active connections and stabilizes the database.

Yes, this Prisma connection pooling guidance applies to Netlify Functions using MySQL or PostgreSQL. It enforces safe client lifecycle practices and datasource configuration to mitigate connection leaks under high concurrency.

To verify that Prisma connection pooling prevents leaks under high concurrency, follow the provided verification guidance to validate that active database connections stay strictly within configured limits during load testing.

You do not strictly need Prisma Accelerate to prevent connection pool exhaustion in serverless apps. You can alternatively use PgBouncer or similar pooling infrastructure alongside a singleton Prisma client to cap active connections.