managing-client-lifecycle

Prevent connection leaks by configuring graceful PrismaClient shutdown with disconnect handlers. Implement shutdown hooks in your server (Express, Fastify) and test teardown (afterAll) to ensure $disconnect() is called before process exit, with a 10-second force-exit timeout to catch missed connections.

Attach PrismaClient shutdown logic to server lifecycle events. Register a shutdown handler that calls $disconnect() when the server closes, ensuring clean termination of database connections before the process exits.

Configure environment-based logging in PrismaClient using the log option to set different levels for development and production. This satisfies observability requirements and helps track connection lifecycle events across environments.

Yes. Add afterAll hooks in your test suite to call $disconnect() and ensure database connections close after tests complete, preventing connection leaks and resource exhaustion across test runs.

Serverless functions require explicit $disconnect() calls before returning, since the runtime may terminate unexpectedly. Implement shutdown logic in your function handler to clean up connections and prevent dangling database sessions.