Google Cloud Datastore vs. MySQL

I feel like Google Cloud Datastore is well suited when the data models are simple and the possible filtering and sorting operation are not complex. With more complex filtering, the amount of required indexes increase, and so does the costs.

Incentivized

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.

Incentivized

• It is hosted in GCP, our primary cloud provider.
• It integrates with all the services we use in GCP.

Incentivized

• Stable - it just runs, with minimal downtime or errors
• Fast - well-structured data is quickly written and read
• Secure - MySQL is easy to keep data secure from people and applications that shouldn't see it
• Easy to use - SQL is industry standard so no problems with adding, editing and reading data stored in MySQL

Incentivized

• Part of the Google Cloud Platform walled garden.
• Pay for read/writes to the datastore, in addition to storage.
• Not many libraries exist.

Incentivized

• 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.

Incentivized

I give Google Cloud a full score because it satisfies our needs so well. We host most of our infrastructure on Google Cloud and using Google Cloud Datastore helps us to solve our NoSQL storage problem. and Google Cloud Datastore is so scalable and elastic. It saves us lots of time to maintain and saves us money.

Incentivized

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.

Incentivized

The simple implementation, together with the Google Cloud dashboard that allows data inspection, editing and querying, makes Google Cloud Datastore a comprehensive choice when it comes to NoSQL databases.

Incentivized

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.

Incentivized

1. Estimate your data size. 2. Test, test, and test.

Incentivized

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. In our case, we've been using Google Cloud Datastore for 4 years without any issues and have never had to think about it.

Incentivized

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.

Incentivized

• It solves our NoSQL database problem.
• It it highly scalable and available to meets our needs.

Incentivized

• As it is an open source solution through community solution, we can use it in a multitude of projects without cost license
• The acquisition by Oracle makes you need to contract support for the enterprise version
• If you have knowledge about oracle databases, you can get more out of the enterprise version

Incentivized