Struggling trying to look for a solution for mysql on AWS and serverless functions on Vercel, looks like RDS proxy won't work 😅 https://www.prisma.io/docs/guides/deployment/deployment-guides/caveats-when-deploying-to-aws-platforms#aws-rds-proxy does anyone have a solution?

We’re currently working on a solution as part of the Prisma Data Platform. You can sign up for early access here: https://pris.ly/prisma-data-proxy

Thanks! This looks interesting, do you know if this would work in the specific situations where a regular aurora database (not serverless) is on RDS and a Next application on Vercel?

Yes this would work for simple RDS databases as well not specific to Aurora Serverless 🙂

Cool thanks! I signed up for it since I'm currently stuck 😅

Any rough idea for early access here? We're definitely stuck on the world of connection exhaustion right now as well 🙂

pgBouncer is def a solution if you can afford it, if you’re on short terms, not going serverless seems to be the easiest solution :/

Lol, that's probably a bit too late - would have to at least rework a little too much to switch away from lambda at this point

@aniraga 👋 Either PgBouncer or using Aurora Serverless should help here.

In theory @aniraga - but it is very simple to leak connections in other ways. That concurrency limit only refers to "active" lambdas as far as I know, so there is nothing stopping them from having e.g. 600 more inactive ones that also all keep a connection open and busy. This is more an art than a science unfortunately 😕

Yeah, I think I'm going to go aurora serverless for now as the easier path and then wait for the new data-proxy 🙂