[mrkurt]

RDS runs pretty well! It's just irritating to use.

The good DBaaS give me a lot more power. This is true for Heroku PG, PlanetScale, Supabase, and Crunchy Data. Some of them let me fork a DB to run a PR against, some give me app level features that save me code, etc.

Most modern hosted DBs also let you run your own replicas.

I'm not really complaining about how well RDS works when your app is connected to it and it doesn't failover/go down for maintenance/etc. It works fine as a DB backend. That's just a baseline I don't think is very valuable anymore.

[gingerlime]

we’re using aiven.io and quite happy, although hard for me to compare. you can port across clouds, which is reassuring if we need to switch. Otherwise their support was helpful debugging a couple of db issues (in our own code). Wonder how they compare in this matrix if anyone knows?

no affiliation. just a customer.

[mrkurt]

aiven.io is quite good. They went broad instead of deep, so they're not as good at Postgres as the Postgres specific companies. But they're probably better Postgres than a PaaS can build by themselves.

[gingerlime]

that’s useful to know that others do postges better. We use their redis as well, so in some ways, breadth is useful for them and for us.

at the time we picked aiven, we couldn’t find any redis-specialized hosting with instances in GCP europe if I recall. so their breadth also plays in terms of locating near the customer servers (important for latency)

[pech0rin]

What do you mean? RDS lets you run replicas

[mrkurt]

RDS will manage replicas for you. But you can't run your own non-rds replicas.

[sandGorgon]

correct. RDS does not even let you do a true, vanilla postgres backup to s3. the lock-in is complete

[pech0rin]

You can easily use pg_dump to do a "vanilla" backup to s3. Its a managed db service but if you wanted to run your own you can extract your data and move to a new db. The lock is not "complete" you are acting like you can't even extract your data.

[0xCMP]

i believe they're taking about being able to ship wal to s3 so the back up is close to real time.

[mrkurt]

"Only export your data with pg_dump" is one of those misfeatures that makes RDS mediocre. They don't really expose much of the power of the underlying DB.

[sandGorgon]

you cannot ssh to RDS machine. so u need to get another EC2 machine and pg_dump over the network. the connection breaks - yes has happened to us multiple times.

RDS makes it very inconvenient to do anything other than use their managed services.

because RDS backup data storage is VERY EXPENSIVE even compared to s3. this is very deliberate.

[dikei]

Using pg_dump for migration of large DB is very difficult due to the downtime it might involve.

[musicalmindz]

This is exactly the issue I have right now on Aurora. We have a 30TB db and there's no easy way to export it to S3 for backup. The closest we have found is this... https://docs.percona.com/percona-xtrabackup/2.4/xbcloud/xbcl...

Anyone else have any idea if there's a better option??