MySQL Reviews

A bit on the more complex side, but definitely one of the more popular solutions between our customers. As a stable alternative to the sometimes really pricy Oracle DB, it performed well for most of our not-database-heavy projects. It was a bit slower than no-SQL solutions on no-SQL tasks, but that's natural I think.

MySQL provides the option to reduce support and maintenance cost when P0 Level 1 support is not really needed for databases used for noncritical use cases and workloads. Other versions that include Microsoft SQL, Amazon RDS, etc don't provide such options and are overkill. MySQL is also more widely used and easy to hire developers for it than the commercial versions ( Microsoft, Amazon, IBM).

Postgress, AuroraDB

When using MySQL I get Oracle support. MariaDB is not a bad alternative, but it doesn't have the same level of support.

MySQL is not used very often for ML.

We use MySQL because it's easy to set up and use.

Faster and quicker to set up.

I think it is easy to learn when someone with technical skills tries to connect with it, and it is easy to handle data.

MySQL is much more easier to use and set up compared to Oracle

Of course compare to no SQL databases it's slower but there is a completely different use case for them... In my opinion it is better than PostgreSQL, it's easier to configure and has the same performance, or approximately the same. Of course Oracle Database is a way bigger choice, smarter faster etc...

For our needs, MySql was enough and it was better known than the others.

It is one of the tools that we had stopped using some time ago and in the last year we amplified its use thanks to its benefits and new functionalities.

MySQL offers some of the features as Oracle Database 12c, however, there are many crucial ones that are missed. Features such as OLAP, really make Oracle Database 12c a clear winner here. We use both databases in our organization for separate reasons, MySQL for prototyping, and Oracle Database 12c for our production environments.

I would choose Oracle 11g, 12c for more complex ventures which require financials and complex logic. I would choose MySQL for simpler applications which simply need to interface data to a backend. I selected MySQL in this case because it is free and much simpler to install—it comes with a Wizard and does not require a ton of manual intervention and configuration. It simply installs and starts the service. Sure Oracle is robust, my MySQL is simple and better for lighter applications.

Easy to use.
Cost-effective.
Integration with development tools.

I selected MySQL for small and medium companies and software.

MySQL is much more flexible and easy to start using.

MySQL is perceived as less scalable than DB2. DB2 provides for an easy migration up to more scale if it is acceptable or required to remain in the IBM ecosystem, which can scale all the way to z-Series mainframes. For some enterprises like insurance and banking, this is a significant advantage.

MySQL is my favorite database system.

Oracle has tons of SQL features that others do not have (e.g. bulk processing), and the price is good.

Oracle gives more safety as a product provider. MySQL is definitely easier to use and with more concise API.

MySQL is a most generic implementation of a database of a sort that is coherent with major designs of web engines and frameworks. As it works in cross-platform environments and easy to deploy it seems to be a competitive choice and prospective solution for integration into web environment for a purpose of hosting a website.

It is easily available and easy to install and access.

First of all, it's free and open source and MySQL supports more programming languages. The MySQL query syntax is easier to learn compared to other database management software. It also works perfectly with Linux or Unix servers. But compared with others, MySQL runs slow on large tables. If you have transactions with a large amount of data, it can not be done properly. This affects the performance of the screens.