We performed a comparison between Google Cloud Spanner and Google Cloud SQL based on real PeerSpot user reviews.
Find out in this report how the two Database as a Service solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We can scale the solution if we need to."
"The application deployment in the cloud is the best feature of the infrastructure."
"The most valuable feature of the solution is its scalability. Scalability comes with two options, among which Google Cloud Spanner can scale horizontally, compared to other relational databases that scale vertically."
"Google Cloud Spanner is stable."
"The solution is easy to use. I am impressed with the tool's features and functionality."
"It's SQL. SQL is so easy if you know something about databases. It's easy to learn."
"The implementation part of the product was easy."
"The valuable feature of Google Cloud SQL is its high availability option. The product is stable."
"Ease of management and the ability to oversee the statistics of your SQL."
"I found its storage and security to be the most valuable. It was a good experience. It is also very stable and scalable, and its support is perfect."
"The setup was straightforward. Just a couple of clicks, and we were done."
"What I like the most about Google Cloud SQL is that it handles the management, which allows us to concentrate on our applications."
"The tool needs to improve horizontal scaling."
"The cost can be a bit high."
"Google came up with something called Cloud Spanner Emulator, which fails to work like the real product if I want to develop some code and run a database locally on my machine."
"I want to improve the deployment of cameras and surveillance infrastructure."
"I am yet to explore a lot of features that are present in this solution. However, it would be good if more documentation is available for this solution. This would help us in preparing for the certification exam and understand it better. Currently, we don't have much documentation. We do the labs for 20 or 25 minutes, but we can't capture and download anything."
"Google Cloud SQL still needs better connectivity to outside, existing data sources."
"To create a seamless data integration, the title integration of these databases with the data integration platforms is essential. This is what we would like to have in a future release."
"I would like to see better integration with all the different tools on the platform."
"I would like to see better availability of the product in different regions. It should also improve the security with encryption."
"The monitoring part could be better."
"The most challenging part is dealing with legacy data from your old systems and migrating it into the new setup, but once you've completed the data migration, it becomes quite convenient to use."
"In the case of Google, they need to work on a more easy interface for users."
Google Cloud Spanner is ranked 8th in Database as a Service with 4 reviews while Google Cloud SQL is ranked 5th in Database as a Service with 16 reviews. Google Cloud Spanner is rated 9.0, while Google Cloud SQL is rated 8.4. The top reviewer of Google Cloud Spanner writes "A stable and scalable relational database that ensures a return on investment for its users". On the other hand, the top reviewer of Google Cloud SQL writes "An easy-to-use solution with good features and functionality ". Google Cloud Spanner is most compared with Amazon RDS, MongoDB Atlas, Oracle Database as a Service, Oracle Exadata Cloud at Customer and SQL Azure, whereas Google Cloud SQL is most compared with Amazon RDS, SQL Azure, MongoDB Atlas, Oracle Database as a Service and Oracle Exadata Cloud at Customer. See our Google Cloud SQL vs. Google Cloud Spanner report.
See our list of best Database as a Service vendors.
We monitor all Database as a Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.