Google Cloud SQL Review from a daily user
October 02, 2017
Google Cloud SQL Review from a daily user
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with Google Cloud SQL
We have been using it mainly whenever we need structured data.
Use case:
- Historical pricing of products (Archive)
Use case:
- Historical pricing of products (Archive)
Pros
- Super easy to set up: new instance -> Authorization -> play
- Automatic backup every night! (Keeps past 7 days as copy as well)
- Automatic failover, in case your main SQL instance fails, they automatically switch you over.
Cons
- It could be cheaper. Definitely cheaper.
- It could provide more information about failovers.
- It could allow you to customize more.
- Saved about 60% from moving to custom SQL instances
- 99% faster deployment = lower cost for deployment in man-hours
- It is hard to add access while doing development on the go.
I don't know to be honest, but I think ease of use is their #1 feature.
Google Cloud SQL Feature Ratings
Using Google Cloud SQL
3 - Developers in general
1 - We have a dedicated google products engineer
- Ease of use data storage (ie, demos)
- Relational data
- Data that needs easy backup
- For queue services that do not require high load.
- Demos
- Simple access systems
- Secret
- Secret
- Secret
Evaluating Google Cloud SQL and Competitors
Yes - It replaced a normal instance of a MySQL service on the servers and added a really good performance. It replaced regular instances of VPS with mysql and Apache.
- Price
- Product Features
- Product Usability
- Vendor Reputation
I would have used a failover from the start.
Comments
Please log in to join the conversation