Google Cloud Datastore is a NoSQL "schemaless" database as a service, supporting diverse data types. The database is managed; Google manages sharding and replication and prices according to storage and activity.
N/A
MySQL
Score 8.3 out of 10
N/A
MySQL is a popular open-source relational and embedded database, now owned by Oracle.
N/A
Pricing
Google Cloud Datastore
MySQL
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Google Cloud Datastore
MySQL
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Google Cloud Datastore
MySQL
Considered Both Products
Google Cloud Datastore
Verified User
Engineer
Chose Google Cloud Datastore
If deploying an application in Google Cloud Platform, using Google Cloud Datastore is a no brainer because of the simplicity of setup. Other options would require more setup and configuration, and do not come with the same level of guaranteed uptime as Google Cloud Datastore. …
MySQL was the first option due to the existing knowledge, and after using other databases, it also appeared to be the most predictable in terms of costs
If you want a serverless NoSQL database, no matter it is for personal use, or for company use, Google Cloud Datastore should be on top of your list, especially if you are using Google Cloud as your primary cloud platform. It integrates with all services in the Google Cloud platform.
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
Learning curve: is big. Newbies will face problems in understanding the platform initially. However, with plenty of online resources, one can easily find solutions to problems and learn on the go.
Backup and restore: MySQL is not very seamless. Although the data is never ruptured or missed, the process involved is not very much user-friendly. Maybe, a new command-line interface for only the backup-restore functionality shall be set up again to make this very important step much easier to perform and maintain.
For the amount of use we're getting from Google Cloud Datastore, switching to any other platform would have more cost with little gain. Not having to manage and maintain Google Cloud Datastore for over 4 years has allowed our teams to work on other things. The price is so low that almost any other option for our needs would be far more expensive in time and money.
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
We have never contacted MySQL enterprise support team for any issues related to MySQL. This is because we have been using primarily the MySQL Server community edition and have been using the MySQL support forums for any questions and practical guidance that we needed before and during the technical implementations. Overall, the support community has been very helpful and allowed us to make the most out of the community edition.
We selected Google Cloud Datastore as one of our candidates for our NoSQL data is because it is provided by Google Cloud, which fits our needs. Most of our infrastructure is on Google Cloud, so when we think about the NoSQL database, the first thing we thought about is Google Cloud Datastore. And it proves itself.
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.