Hey @betocmn, you’re correct about RDS proxy, as David mentioned, we ended up using digital ocean’s managed DB. Some other options we explored:
This looks very promising and cost effective, but at the time it was missing something we needed (can’t remember what)
- connecting directly to AWS RDS
In terms of performance, we are indeed very happy with DO. I did some testing against an authenticated graphql endpoint and roughly we saw without connection pooling we were getting 10-30 responses concurrently per second, before the db connection started erroring out (on small instances). With pg_bouncer on digital ocean, the DB didn’t flinch, we kept going something like 80-150 TPS, and that too only because cloudflare/netlify was throttling requests (my tests weren’t very sophisticated).
My partner @iggy was meant to write a guide about it - sure he’ll get round to it soon.
If you’re up for it, you could also setup your own instance of pg_bouncer on AWS to use with RDS.
Just a headsup - I’m not a DB or infrastructure expert :). Please do let us know how you get on!