This is an oversimplification, but! Dumping postgres to a file is one command. scp the file to a different server is two commands. (Granted you need to setup ssh keys there too). I have implemented backups this way.
With sqlite you only need the scp part.
You can even push your backup file to an S3 bucket... with one command!
Honestly, this argument mystifies me.
Of course you can make it as complicated as you want to, too. I've also worked on replicating anonymized data from a production OLTP database to a data warehouse. That's a lot more work.
> Our backups to S3 apparently don’t work either: the bucket is empty
It took them a data loss incident to find this out? This is just one of the many red flags mentioned in the article, IMO this incident isn't about relying on cloud backups vs self managing it
With sqlite you only need the scp part.
You can even push your backup file to an S3 bucket... with one command!
Honestly, this argument mystifies me.
Of course you can make it as complicated as you want to, too. I've also worked on replicating anonymized data from a production OLTP database to a data warehouse. That's a lot more work.