Currently, TencentDB for MySQL supports MySQL v8.0, v5.7, v5.6, and v5.5. For more information on the features of each version, please see the official documentation. MySQL's official lifecycle support policies are as shown below:
|Release||GA Date||Premier Support End||Extended Support End||Sustaining Support End|
|MySQL Database 5.0||Oct-05||Dec-11||Not Available||Indefinite|
|MySQL Database 5.1||Dec-08||Dec-13||Not Available||Indefinite|
|MySQL Database 5.5||Dec-10||Dec-15||Dec-18||Indefinite|
|MySQL Database 5.6||Feb-13||Feb-18||Feb-21||Indefinite|
|MySQL Database 5.7||Oct-15||Oct-20||Oct-23||Indefinite|
|MySQL Database 8.0||Apr-18||Apr-23||Apr-26||Indefinite|
- The extended official support for MySQL v5.5 ended in December 2018. There has been no explicit statement on further support extension, which is possibly because fixing issues takes more time. We strongly recommend that you use a higher version of MySQL.
- MySQL v5.6 and higher no longer support the MyISAM storage engine, so we recommend that you use the InnoDB engine, which features better and more stable performance.
- Currently, MySQL v5.6 and higher support three replication modes: async, semi-sync, and strong sync. Only async mode is available in MySQL v5.5.
|Feature||TencentDB for MySQL v8.0||Oracle MySQL v8.0|
|Cost performance||1. Elastic resources.
2. Tencent's kernel TXSQL.
3. The backup and restoration features are already integrated.
4. A complete set of SaaS tools and services.
|1. The one-time investment cost is huge.
2. The open source version has no performance optimization.
3. You need to deploy backup resources by yourself, which incurs additional costs.
4. You need to pay for public network traffic as well as high domain name fees.
|Availability||1. A complete high-availability switchover system is provided.
2. Read-only instances automatically balance load and traffic.
3. Disaster recovery instances are provided for remote disaster recovery, ensuring high availability.
|1. You need to buy servers and wait for the delivery.
2. You need to deploy the high availability and load balancing systems by yourself.
3. It costs a lot to build data centers in multiple regions.
|Reliability||1. Data reliability of up to 99.9996%.
2. Low RPO/RTO.
3. Stable source-replica data replication.
|1. Data reliability of 99%, which depends on the probability of damage to a single disk.
2. You need extra R&D investment to achieve a low RPO.
3. Data replication delays or interruptions may occur.
|Ease of use||1. A complete set of database management services are provided and databases can be easily operated in the console.
2. Seconds-level monitoring and intelligent alarms.
3. An automatic multi-AZ high availability system.
4. One-click version upgrade.
|1. You need to deploy high availability and backup and restoration systems by yourself, which requires time and money.
2. You need extra investment to purchase a monitoring system.
3. It costs a lot to set up data centers in different regions with labor costs in OPS.
4. The version upgrade cost is high and the maintenance needs a long downtime.
|Performance||1. Local SSD disks have excellent performance and the custom hardware supports fast iterations.
2. The optimized TXSQL ensures high performance.
3. DBbrain supports the intelligent diagnosis and optimization of MySQL.
|1. Oracle MySQL has a slower hardware iteration speed than that of cloud computing, usually resulting in lower performance.
2. It can be costly as databases rely on senior DBAs.
3. Oracle MySQL does not have native performance tools, so you have to purchase or deploy them by yourself.
|Security||1. Prevention in advance: allowlist, security group, VPC-based isolation.
2. Protection during the database operations: TDE + KMS data encryption.
3. Auditing after the database operations: SQL auditing.
4. TencentDB for MySQL is updated right after the Oracle MySQL has security updates.
|1. The cost of the allowlist configuration is high and the private network needs to be implemented by yourself.
2. You need to implement encryption by yourself during the database operations.
3. It is difficult to audit SQLs after the database operations as the open source MySQL does not support SQL auditing.
4. Once MySQL updates, OPS will be required to install updates or databases will have to be shut down for maintenance.