Why MySQL is not used in Environment Analysis

When I was managing a technical consulting company, I heard some reasons for not using MySQL. Although many reasons are due to misunderstanding, there are indeed some reasons for not using MySQL. Of course, the actual situation may vary depending on the environment, but in each case, I think that rejecting any database technology should be based on reasonable reasons, rather than relying on some exhausting database administrators (DBAs). For this purpose, I listed eight reasons for not using MySQL in this article.

First, the reasons for not using a technology are essentially different from those for using it. Often, the reasons for opposing something are even more noteworthy. We may need several reasons to actually use this technology, but it will stop us for one reason. Software selection is such a decision. The only reason is that it is not enough to make a positive decision, but a good negative reason denies many positive factors.

Although there is a long string of relational database management systems (RDBMS) for us to choose from, I will limit the comparison to several of the most commonly used products. Although there are few comprehensive comparisons, there are still many technical comparisons. Here, we only care about the "formal" reason.

MySQL uses GPL

The most important reason is the priority. It is not suitable for GNU General Public License here, and it should not be the choice of database technology. Obviously, GPL licenses are positive for many environments, but for some other environments, GPL software is hopeless. In these cases, the BSD license for connecting to PostgreSQL is still too "open", so a commercial license will be more suitable.

MySQL does not use GPL

In some cases, MySQL charges fees, so GPL may not be able to serve these situations well. If you want to sell the database license with your own project, you must use a similar license for your project, or you need to purchase a commercial license. If this factor changes the way your software is sold, you need to handle the extra burden caused by the need to support multiple MySQL versions or configurations (this will increase end user costs ), or there is an unreasonable impact caused by the use of MySQL. Under these circumstances, some software distributors may prefer to use other products, such as PostgreSQL with a BSD license.

Integration with existing environment

I know that large IT companies have Site licenses for Oracle and Sybase, and many MS-SQL Server licenses ). In these companies, the instance of this MS-SQL is mainly caused by the ignorance of the departments staff, they do not know they have spent money to buy other databases site license. In this environment, it is unwise to add MySQL (or other databases). If DBA already has too many environments to handle. If an existing database is maintained on a general platform, the maintenance burden is obviously reduced. Further, if the company already has a license to use a private system, the main reason for using MySQL does not exist.

1 2 3 Next Page

[Content navigation]
Page 1st: Why MySQL is not used in Environment Analysis	Page 2nd: Why MySQL is not used in Environment Analysis
Page 3rd: Why MySQL is not used in Environment Analysis