When comparing Google Cloud SQL vs Sodadb, the Slant community recommends Sodadb for most people. In the question“What are the best SQL Database as a Service providers?” Sodadb is ranked 9th while Google Cloud SQL is ranked 10th. The most important reason people chose Sodadb is:
Allows users to fill in an online form.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Supports automatic encryption
Google Cloud SQL automatically encrypts all tables and temporary files.
Pro Forms
Allows users to fill in an online form.
Pro Simple
Database can be shared as an URL, or accessed via an API.
Cons
Con AWFUL data integrity practice: Backup lifecycle is tied to instance lifecycle
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/backups#about_on-dem
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 must:
Don't fall for it. Protect your production data. Avoid busywork caused by poor product design. Avoid Google CloudSQL.
Con Performance limits
There are some performance limits when dealing with transactions for Google Cloud SQL.
Con Not much storage space
The default free 10 Mb storage space sounds a bit pathetic.
Alternative Products
