I was excited for V2 but honestly my experience with V1 was very subpar and I ended up moving to PlanetScale instead of continuing to work around their frustrating limitations and high costs.<p>V2 has DOUBLED in price and while you can now adjust it in .5 "ACU" it's dead on arrival for me. Honestly V1 was way too expensive for what you got in my opinion. Having to deal with Dev/QA environments sleeping was a huge PITA (sorry, I'm 1 developer, I can't pay 3x$45/mo, even keeping prod up was expensive). Scaling up was SLOW and often failed, I ended up just scaling up super high before my event that used my product because I was worried it wouldn't scale up automatically. In my testing I always had to stop using the DB for a while before it would finally scale up.<p>As for my Dev/QA environments, I was able to wake them from sleep when you hit the client app but it would take almost a minute to wake. In order to save money I had those environments sleep after 5 minutes of inactivity. Maybe it would have been better if I raised that to 10-30min but I'd regularly finish writing some server/client code then go to use it and realize the DB went to sleep on me and have to wait on it.<p>With PlanetScale it's $30/mo and I can have Dev/QA Branches that don't cost me any extra. Not to mention they actually seem to understand the need for things like lots of connections. I had read not great things about Aurora handling a ton of Lambdas connecting to them and so I wrote the first version of my product using their data-api which was a mistake. Since then I've moved to using Primsa as my ORM and you can throw literally a quarter of a million connections at PS without issue [0].<p>I almost built on top of Aurora Serverless V2 when it was in beta and I'm so glad I didn't and that I found PlanetScale when I did.<p>[0] <a href="https://planetscale.com/blog/planetscale-vs-aws-rds" rel="nofollow">https://planetscale.com/blog/planetscale-vs-aws-rds</a><p>> While RDS limits connections to 16,000 PlanetScale has been designed to scale upwards of 250,000 connections to a single database. Theoretically we can handle millions of connections-- but 250,000 is a real world number.