Step 11: select the most stable MySQL version

MySQL open-source database has multiple important branches: MySQL Cluster, MySQL 5.1, MySQL 5.5, and MySQL 6.2. Each branch has the same MySQL database version: Development version, Alpha version, Beta version, RC version, and GA version.
The Development version, Alpha version, and Beta version are generally not used in the project. Because they certainly have major problems or some functions are not fully implemented. In most cases, the RC version is not allowed to be used in the production environment. After all, it is only a small version before the production version is released. Similarly, we must carefully choose the GA version of the MySQL database. After all, open-source community products have not been strictly tested and may have weak stability than commercial products. The selection process for the GA version of www.2cto.com MySQL database is from Oracle's acquisition of SUN and its wholly-owned subsidiary MySQL AB. MySQL AB will no longer contribute source code to the open-source community. At the same time, with the departure of many founders and technicians, we must carefully select the new version released by MySQL AB. Do not blindly trust the test report officially provided by MySQL AB. We recommend that you refer to the following MySQL database GA version selection process, as described below: analyze whether the enterprise business needs to use the basic functions and features of MySQL, the key research direction is: mySQL replication, partition tables, and Plugin-innodb. It takes at least 10 months for the first GA version of the MySQL database product line to be available in the production environment. The latest GA version of the MySQL database product line is generally not the first choice. It may be 3 ~ later than the latest version ~ Four versions of GA databases. Read the GA version of the target database carefully. If a large number of bugs are modified based on the previous version, the GA version should be carefully selected. Read carefully the information of the first version after the GA version of the target database. If the BUG information is very large, discard the target version and push forward a version number as the target version. Follow the steps described in step 4 and Step 5 to select a version that is later than the selected version. The number of bugs is not significant, and there are very few serious bugs, and it is not the latest GA version. Read in detail 2 ~ after the selected database GA version ~ The BUG fix information of the three versions is mainly related to the target GA version, and how to reproduce it and find solutions to circumvent it. Www.2cto.com functional testing and performance testing are required for the GA version selected in the above seven steps, combined with the functions that may be required by the enterprise's business. The selected database GA version, as an internal development and testing database environment, usually takes about 3-6 months for trial run. The new GA version can be considered for non-core businesses of enterprises. After the above 10 procedures, if there are no major functional bugs or performance bottlenecks, you can start to consider as the backend database of all business data services. Many full-time DBAs in enterprises may not have the time, energy, or resources to select versions, and may not be willing to spend so much time. Some enterprises may need to select a database GA version. Some enterprises do not have a full-time DBA, but are replaced by O & M or development engineers, however, they may not be able to select database software versions. Are there any shortcuts for choosing the GA version of the MySQL database? The answer is yes. You can pay more attention to the DBAs of some large companies or well-known DBAs in the industry. You can consult them through multiple channels or consult internal personnel directly, learn the version of their core business database.
Author snoopy7713