Skip to content

Prisma Connection Pool #237

Open
Open
@MarwanRadwan7

Description

@MarwanRadwan7

Describe the Bug (버그 설명)

Creating a new instances of PrismaClient each time with its own connection pool is not efficient in production applications. As for every new instance you make a new connection on the database pool.

Version to Reproduce (현재 사용한 버전)

Version: 10.2.1

Steps to Reproduce (재현 순서)

  1. Go to middlewares, constrollers and services directory
  2. Click on '....'
  3. Scroll down to public users = new PrismaClient().user;
  4. See error

Expected Behavior (예상 동작)

Heavy load on the database.

Solution:

Using some kind of singleton instead so it uses the same instance for all of these.

Metadata

Metadata

Assignees

Labels

🐞 BugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions