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 (재현 순서)
Go to middlewares, constrollers and services directory
Click on '....'
Scroll down to public users = new PrismaClient().user;
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.
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 (재현 순서)
public users = new PrismaClient().user;
Expected Behavior (예상 동작)
Heavy load on the database.
Solution:
Using some kind of singleton instead so it uses the same instance for all of these.