And I seriously question if their cloud offerings have actual product designers attached.
One great example:
If you are using Google CloudSQL, you are one command away from losing everything:
> gcloud sql instances delete prod-instance-name
When you delete a CloudSQL instance, it also deletes the back-ups associated with that instance along with it. So if you accidentally delete your production database: Your backups? Poof. Gone.
It says this in the fine print of the on-demand backups documentation: https://cloud.google.com/sql/docs/mysql/backup-recovery/back...
> They persist until you delete them or until their instance is deleted.
There is also no way to mark a CloudSQL instance as "protected" so one bad CLI command can lose you your production database and all backups.
In order to get an actual backup workflow that will not affect production traffic, you have to script your own database dumps.
For me, Google CloudSQL does not do enough to protect my production data from accidental deletion. I would argue it is unclear how your production backups are being handled. I would argue their product treats your production data and backups irresponsibly.