We use Google Cloud SQL as our primary production Postgres database, as well as our development/staging database. We love it because of its autoscaling features, automated backups, and excellent security. We primarily connect to the database via our Google Cloud Run instance, and it's all securely tied down in a VPC. It also serves well as a development/staging database - we just turn off some of the more premium features like autoscaling.
Pros
Automated backups
Autoscaling functionality
Great security via VPC
Cons
Currently to connect to the database locally, the Cloud Auth tool provided by Google is a bit cumbersome to use, and we end up making more use of "allowed networks" and just enabling our personal IP addresses
Likelihood to Recommend
Google Cloud SQL works perfectly as a production database - it's really got all the features you'd want to have good production-related practices and it stays affordable via autoscaling. It probably would be overkill as a development/staging database, but it's also nice to reuse the same configuration between them.
VU
Verified User
Engineer in Research & Development (Environmental Services company, 51-200 employees)
