Next.js, Prisma and Vercel Postgres Beta needs Prisma Data Proxy for connection managment?
Unanswered
Spectacled bear posted this in #help-forum
Spectacled bearOP
Previously in other serverless projects I have worked on, I have hosted the database in an AWS RDS and this has brought me performance problems with prisma, so I have had to implement a Prisma Data Proxy (https://www.prisma.io/docs/data-platform/data-proxy) to handle the connections to the database of data.
Now I am working on a Next.js 13 project hosted in Vercel and I connect a Vercel Postgres Database (that is in Beta) to it.
My question is if I have to implement prisma proxy data to avoid these problems, or is this solved using this new Vercel Postgres service.
Now I am working on a Next.js 13 project hosted in Vercel and I connect a Vercel Postgres Database (that is in Beta) to it.
My question is if I have to implement prisma proxy data to avoid these problems, or is this solved using this new Vercel Postgres service.
3 Replies
it is solved when deployed to Edge Runtime. In short it connects via websocket, and connection pooling is implemented in Neon server side.
https://neon.tech/blog/serverless-driver-for-postgres
https://neon.tech/blog/serverless-driver-for-postgres
sorry but it is about Postgres. Prisma has another problem with V8 Isolates runtime issue. i guess.