Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Google Cloud SQL vs F(x) Data Cloud, the Slant community recommends F(x) Data Cloud for most people. In the question“What are the best SQL Database as a Service providers?” F(x) Data Cloud is ranked 1st while Google Cloud SQL is ranked 10th. The most important reason people chose F(x) Data Cloud is:
If you wanna host your database on the cloud server, you can have both the option as Database as a Service (Pre-installed and managed database) or Infrastructure as a Service (If you want to have root access and manually want to install the database).
Specs
Question Ranking
Pros
Pro Supports automatic encryption
Google Cloud SQL automatically encrypts all tables and temporary files.
Pro Option for hosting the database service on the cloud server.
If you wanna host your database on the cloud server, you can have both the option as Database as a Service (Pre-installed and managed database) or Infrastructure as a Service (If you want to have root access and manually want to install the database).
Pro High uptime
All the cloud services are with 99.95% uptime.
Pro Cost-friendly
F(x) Data Cloud provides public cloud server at a cheap price. The basic plan starts at $1.99/month.
Pro Great Support
Typically answers in minute.
Pro Provides high configurations
They provide 32 vCPU, 128 GB RAM, 2000 GB SSD, 9 TB network. For large businesses, high configurations are required.
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-nameWhen 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 No GPU provided
GPU is not provided.
