As currently I have developed inventory system, clinic system, an backend application for a private company to manage huge no of memberships and ads, and a UK company for manage Business Name , Limited company, trademark and domain registrations and renewals. All of these used with mysql its those are running smoothly. Never had any headaches as through sql queries can manipulate easily and had fast responses for even complex queries and for huge no of data Frameworks used are spring boot and laravel.
Pros
Known and used by most people as most secure and reliable relational database management system. Accompanies 99.99% uptime. Nothing to fears as open source. Can have millions of helps through community. Offers a wide scope of high accessibility like cluster servers master slave replication. Provides high performance even for large volume projects. Growing and improving frequently. Best for cloud applications and big data applications. Supports by huge no of frameworks.
Cons
Red Hat Enterprise Linux, openSUSE, Fedora, Slackware Linux etc moved to MariaDB.
Rating breakdown
Likelihood to recommend: 10/10
I've been using MySQL for 12+ years. It was great then and it's great now. Lots of features have been added and query speed has been improved by a lot. Since it's a software that has been around us for many years, I insist, the backwards compatibility isn't the desired one, all the needed adjustments to datasets generated in old versions (that are still running in production environments) rely on the dba. Would be great if there could be a utility that handles that.
Pros
I like that it has a community edition which allows to get the software for free with community support. In the case of red hat/CEntOS host, a repository settings can be added and the installation is pretty straightforward.
As long as it is correctly setup according to the server resources and expected demand, it runs pretty fast, it is stable and supports lots of connections.
Cons
I feel that it has been starting to loose its backwards compatibility. If you need to use a previous feature, for example, if you want to use the mysql native password, now you need to specify it when creating a user, otherwise, it won't work straightforward with most CMS software. Also, as some datatypes are being improved (which should be a nice to have feature), when migrating to a newer version, restoring a dump can turn into a headache. The users model have also changed, so, if you had a very large users set, you have to do some work to make it work again in newer versions.
Rating breakdown
Likelihood to recommend: 9/10
I am saving disk space. I am experiencing fast database server. I am experiencing the compatibility with multiple operating systems.
Pros
I like most the speed of MySQL and capability to support multiple kind of operating systems on various machines
Cons
I don't find anything to dislike in MySQL till yet in my throughout experience.
Rating breakdown
Likelihood to recommend: 10/10
We just use MySQL for all of our databases
Pros
It's the default standard for many companies. MySQL has grown into a very stable product that never crashes. We've made the move to MariaDB, but found that the tables sometimes get corrupted when restarting a database server under heavy load. With the recent speed improvements to MySQL, we have decided to actually migrate back to MySQL.
Cons
I'd really like if they would spend a bit more time on their CLI interface. As in, syntax highlighting in the CLI, an easier way to scroll through multiline queries when going through the history. I would also like it if we can specify a color scheme to use for the output.
Rating breakdown
Likelihood to recommend: 10/10
I use MySQL in many personal projects, like my automated house project. It was a very good choice, I'm happy with this. Also, in the past, I have worked with MySQL and PHP in my company's intranet page. It was a good tool, but as the company grows, we need to migrate to another platform. Also, it is important to say that if you use the correct database engine with MySQL, you can have foreign keys and other types of constraints so it is very flexible.
Pros
MySQL is a well balanced product, while it is free to use, it also has many features you can find in corporative solutions, like SQL Server and Oracle. If you ever need help, you will find answers almost everywhere, from their own documentation to stackoverflow and other forums, easily. You will have a very short learning curve with MySQL.
Cons
When you need to deal with great amount of data, like some kind of data warehouse structure or huge amount of measures to analyze, you better go other choices. It starts getting too slow with the same hardware other products will work smoothly. But I guess that is not the purpose for MySQL. In the other hand, if you want it to build a transactional system like an e-commerce platform or even a Blog page, it is a very good choice!
Rating breakdown
Likelihood to recommend: 10/10
MySQL offers a free trial for new users, after which the software is available across 4 commercial editions. Pricing and functionality are outlined below.
MySQL Cluster Carrier Grade Edition Subscription (1-4 socket server): starts at $10,000 per year
MySQL Cluster Carrier Grade Edition Subscription (5+ socket server): starts at $20,000 per year
MySQL Enterprise Edition Subscription (1-4 socket server): starts at $5,000 per year
MySQL Enterprise Edition Subscription (5+ socket server): starts at $10,000 per year
MySQL Standard Edition Subscription (1-4 socket server): starts at $2,000 per year
MySQL Standard Edition Subscription (5+ socket server): starts at $4,000 per year
MySQL Classic Edition (only available for ISVs/OEMs)
Australia (English)
Canada (English)
Deutschland (Deutsch)
United Arab Emirates (English)
España (español)
France (français)
Ireland (English)
México (español)
Nederland (Nederlands)
New Zealand (English)
Österreich (Deutsch)
Portugual (Português)
Singapore (English)
South Africa (English)
United Kingdom (English)