Am I making too many PrismaClient objects?
I am working on a multi-tenant application.
I have two separate routers. One for cross-tenant queries and mutations named
I created a Prisma extension to insert a where clause in all queries. The extension needs a facilityId from each request.
Because of this, I am calling the following code inside of
Does createTRPCContext run on every request to the API?
Am I creating a new Prisma client on every request?
My goal is to have cross-tenant data safety baked into the application. I want the API interaction from the front-end code to be very explicit.
The
This application will be in a regulated environment so I will be hosting on AWS ECS and RDS.
Another option I am considering is Supabase and using RLS.
Thank you.
I have two separate routers. One for cross-tenant queries and mutations named
adminfacilityI created a Prisma extension to insert a where clause in all queries. The extension needs a facilityId from each request.
Because of this, I am calling the following code inside of
createTRPCContextDoes createTRPCContext run on every request to the API?
Am I creating a new Prisma client on every request?
My goal is to have cross-tenant data safety baked into the application. I want the API interaction from the front-end code to be very explicit.
api.admin.users.getAll() // Obviously a cross-tenant API callapi.user.getAll() // Obviously a single tenant API callThe
adminadminProcedureThis application will be in a regulated environment so I will be hosting on AWS ECS and RDS.
Another option I am considering is Supabase and using RLS.
Thank you.
