DB-001 critical general
Connection pooling and optimization configured
Verify Prisma connection pool is explicitly configured with pool size, connection timeout, and idle timeout settings.
Question to ask
"What happens to your DB when traffic spikes unexpectedly?"
Verification guide
Severity: Critical
Check automatically:
Look for Prisma schema database config:
grep -r "connection_limit\|pool_timeout" prisma/schema.prismaCheck DATABASE_URL for pool parameters:
grep -E "connection_limit|pool_timeout|connect_timeout" .env.example .env.local 2>/dev/nullLook for Prisma client instantiation with explicit pool config:
grep -r "new PrismaClient" --include="*.ts" --include="*.js" -A 10
Pass criteria:
- Pool limit explicitly configured (not using defaults)
- Connection timeout configured
- Idle timeout configured
Fail criteria:
- No pool configuration found
- Using default/unlimited connections
- No timeout settings
Evidence to capture:
- Pool size setting
- Connection timeout value
- Idle timeout value
- Location of configuration