Skip to content

[Backend] No database connection pooling configured — PrismaClient instantiated per request in some services #635

Description

@Pvsaint

Problem

Several services instantiate new PrismaClient() locally rather than importing the shared singleton. Each instantiation creates a new connection pool, rapidly exhausting PostgreSQL's connection limit under load.

Acceptance Criteria

  • A single shared prisma singleton exported from src/config/prisma.ts (or equivalent)
  • All services import the singleton instead of instantiating their own
  • prisma.$disconnect() called only in shutdown.service.ts, not in individual services
  • DATABASE_URL connection string includes connection_limit parameter appropriate for environment
  • Load test verifies no connection exhaustion under 100 concurrent requests

Branch & Commit

branch: fix/prisma-singleton-pool
commit: fix(database): enforce single PrismaClient singleton across all services

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions