Connection string clarity when using Prisma
I've a a couple of servers that connects to Supabase using Prisma. Now i've read the integration with prisma guiide, but i'm little confused hence the question.
Note: Database migrations are handled by Prisma.
Deployment scene
1. Some api servers are containerized and deployed on AWS ECS with fargate.
2. Some api servers are containerized and deployed on AWS Lightsail containers.
3. Few of them are running on bare bones EC2
Now I wanted to understand what connection string should be best for these deployment use-cases.
Should I use session pooler or transaction pooler with or without direct url.
It would be great if I can get some clarity.
Note: Database migrations are handled by Prisma.
Deployment scene
1. Some api servers are containerized and deployed on AWS ECS with fargate.
2. Some api servers are containerized and deployed on AWS Lightsail containers.
3. Few of them are running on bare bones EC2
Now I wanted to understand what connection string should be best for these deployment use-cases.
Should I use session pooler or transaction pooler with or without direct url.
It would be great if I can get some clarity.
