When comparing Google Cloud SQL vs QuintaDB, the Slant community recommends QuintaDB for most people. In the question“What are the best SQL Database as a Service providers?” QuintaDB is ranked 3rd while Google Cloud SQL is ranked 8th. The most important reason people chose QuintaDB is:
Offers a [REST API](https://quintadb.com/api/index).
Ranked in these QuestionsQuestion Ranking
Pro Supports automatic encryption
Google Cloud SQL automatically encrypts all tables and temporary files.
Pro REST API
Offers a REST API.
Pro Import / Export
Excel, CSV or txt data.
Pro Access rights
Access rights management for teamwork.
Pro Email notifications
Email can be sent when a html form has been submitted.
Pro Can be used for free
The free version offers 3 GB storage, but is limited to 2000 records.
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.