The web/infra team uses Google Cloud SQL as a managed MySQL database for most of our staging/testing environments. We have an array of internal tools that depend on a MySQL database. It addresses our need to store relational data for the tools and services that we build around our product(s)
Pros
Easy to set up
Provides a good web interface to monitor resource consumption
Has built in backups and replication support
Cons
Connection options. Currently, only connections via sockets are supported if using with CloudRun
Connection drops during maintenance
Costs escalate quickly when usage grows
Likelihood to Recommend
It is well suited if already working in a Google Cloud environment with multiple other Google Cloud services. For example, when setting up a cloud run application, it has a build in connector to Cloud SQL if the application requires one. It isn't well suited in a multi cloud or hybrid cloud environment
VU
Verified User
Team Lead in Engineering (Computer Games company, 501-1000 employees)
Basically I use Cloud SQL comes with the capabilities such as cloud storage, strong backend and fast quires compilation features that's make it a best and suitable tool. It has helped us automate a lot of our reporting processes and has helped us optimize our team effectively.
Pros
Automation of tasks
It has a easily and user understandable interface which provides it every necessary feature to come up with.
Monitoring tools
Cons
Defragmentation tools
The data integration feature can be done for different erp system.
more information on how to use the product
Likelihood to Recommend
Great for web apps and smaller projects but not ideal for huge data or ultra-low-latency needs.
We have migrated most of our self-hosted versions of MySQL and Postgres to Cloud SQL as it helps in managing the databases without having to maintain them on VMs. This has freed a lot of time of our devops team and they can spend more time on the overall solution vs the database management.
Pros
MySQL
Posgres
Backups
Cons
SLA
Maintenance windows
Backward version support
Price
Likelihood to Recommend
It is very well suited for teams who just want to get things done. Teams which don't want to take the headache of running their own databases, this is the go to service. GIven it is a hosted service by Google, it comes with the benefits of automated security updates, uptime management, backups are pretty easy and so are the restores.
VU
Verified User
Vice-President in Engineering (Computer Software company, 201-500 employees)
In our organization we need to store a large amount of data that is very efficient to access. For this reason we need a managed relational database that is easy to scale and manage.
For this reason we opted to use a PostgreSQL database that is managed by Google Cloud SQL.
Pros
Interface
Scalability (Autoscaling)
Price
Support team
Cons
Limited customization
Likelihood to Recommend
It's definitely suited for companies that needs a very efficient and performant database with the option to scale the server based on needs.
It might not be really appropriate, on the other hand, for smaller companies that do not expect an high usage of such database.
VU
Verified User
Engineer in Engineering (Computer Software company, 11-50 employees)
We use Google Cloud SQL with Mysql Engine as the primary Database for storing Application Data. Our compute engine are connected to the SQL Cloud. We also use it to store the summarised data for MIS & Reporting.
Pros
Handle Transactions
MIS & Reporting
Maintain Structured Datasets
Cons
Better Control over ACL
Add replication factor to have a Readonly Reporting DB
Likelihood to Recommend
Pros - Great for storing Structured dataset - Handling Transaction based workflows
We use it as the main SQL database for our SaaS. The server is hosted on Cloud Run (serverless) and connect direcly using private IP inside the VPC. It supports high availability and read replicas, as Pitr backup recovery and logs/metrics integrated to Google Cloud monitoring.
Pros
Pitr backups
High availability
Read replicas
Log and monitoring
Cons
SSL certificates are self signed, most services dont support them
Cant query high availability replicas [in my experience]
Likelihood to Recommend
For a general purpose SQL database, it's very well suited, performant and secure, if you already use GCP. If you intend to connect from other BI, analytics or 3rd party tools, I advise to check if they support SSL to Google Cloud SQL, because most don't. If you are on AWS, go with RDS
I have worked with Google Cloud SQL for a R&D project. I was given the task to implement a data conversion application. we wanted to migrate from an on-prem SQL database to Google Cloud SQL. we decided to use Google SQL. It supports all the relational database needs. It is a fully managed and secure service.
Pros
It is fully managed
It is easy to setup
It provides high speed data transfer
Cons
[I feel] It needs more integrations
[I feel it] Needs to work on price structure
Likelihood to Recommend
It is a very powerful database service. It can be easily set up even by an entry-level developer. It can be used by medium to large organizations in their various projects. It can be used by business apps as well at any level. It can also be used where latency is an issue as It is extremely fast
VU
Verified User
Engineer in Information Technology (Computer Software company, 501-1000 employees)
Google Cloud SQL is used across technology, analytics and BI teams to store relational databases, tables, and run queries to fetch data from these databases.
Business problems addressed:
Joining data tables from different databases to give a combined view of attributes and records
Run SQL queries to fetch raw data and prepare product usage reports on top of it
Prepare an automated data API workflow to be sent directly to BI systems to generate automatic reports
Pros
Very easy to use and migrate existing database systems to Google Cloud SQL system
Easy to query with real-time query assessment as well as processing metrics to help optimize the queries
No need to learn any other querying language (like in Hadoop ecosystem), as SQL works pretty fine
Easy-to-use GCP portal to type in queries and see the results on the screen (no need to go on command line )
Easy to set up
Cons
Lack of latency with quota size increasing
Can't customize an instance’s IP
Bit more expensive than some other players in the market, for instance, while downloading information
Likelihood to Recommend
Well suited for relational database storage and connections
Supports well-built APIs, which ensures easy access
Automatic failover (moving an application to a standby Google Cloud SQL server in case an instance fails)
Works really well with other Google Cloud products like Compute Engine, AppEngine, Kubernetes, etc.
Google Cloud SQL (MySQL) is used as the relational data store for our product. The ability to scale up, have read replicas, and have automatic failover built into the offering are really nice features. The automated backup feature is nice as well. To have 7 days of backups available at any time without having to support the processes necessary to make that happen is great.
Pros
Automatic failover to another region in case the database goes down.
Easily scale the instance up if more processing power or memory is required.
Cons
Automatic backup validation. The backups are performed on a daily basis within the selected window, however, they are not validated. This means the backup could be reported as successful but ultimately be unusable in a situation where it is needed. We got around this issue by periodically validating on our own by spinning up a box, restoring the backup to the new instance, and then destroying the instance after validation. It's not perfect, but is a good sanity check to make sure our backups are valid in case we do need them.
Likelihood to Recommend
It is great if you don't want to worry about managing hardware and infrastructure and instead focus your efforts on work directly related to your product's database needs, i.e. schema design, efficient queries, etc. However, if you are dealing with very large data sets, then BigQuery, BigTable, or similar might be better suited for your needs.
VU
Verified User
C-Level Executive in Information Technology (Computer Software company, 11-50 employees)
[We're] using it as the primary database supporting multiple WordPress installations that are running on Google Cloud. It's being used for every site that we currently have on Google Cloud, and are in the process of moving more sites over to this platform. Having everything on Google's infrastructure makes everything easy to manage and Google Cloud SQL is insanely fast.
Pros
It's insanely fast.
Easy integration with Google Cloud hosted services.
It's backed by Google's infrastructure, which is always good.
Cons
Connecting to it for the first time is a little confusing.
An interface for interacting with the data would be awesome.
Likelihood to Recommend
If you're hosting a site on Google Cloud, it only makes sense to make use of Google Cloud SQL for the database, as opposed to running a separate MySQL service on a VM. It's extremely fast and has resulted in a dramatic improvement in page load time across multiple sites.
