- Release Notes
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Purchase Guide
- Get Started
- Operation Guide
- Best Practice
- Usage Specifications of TencentDB for MySQL
- Creating VPCs for TencentDB for MySQL
- Increase Business Load Capacity by MySQL Database
- Deploying Python Web Applications
- Build LAMP Stack for Web Application
- Build Drupal Website
- Configuring Application Automatic Reconnection
- Limits on Automatic Conversion from MyISAM to InnoDB
- Impact of Modifying MySQL Master Instance Parameters
- Call MySQL API by Python
- White Paper
- API Documents
- History
- Introduction
- API Category
- API Call Requests
- Task API
- Security API
- Database API
- Account API
- Monitoring APIs
- Parameter APIs
- Backup APIs
- Data Import APIs
- Instance APIs
- CreateRoInstanceIp
- BalanceRoGroupLoad
- AddTimeWindow
- CreateDeployGroup
- DescribeDBInstanceInfo
- DeleteDeployGroups
- DeleteTimeWindow
- CloseWanService
- DescribeRoMinScale
- DescribeRoGroups
- CreateDBInstanceHour
- DescribeDBInstanceCharset
- DescribeDBInstanceConfig
- DescribeDeployGroupList
- DescribeDBInstanceGTID
- DescribeDBInstanceRebootTime
- DescribeTagsOfInstanceIds
- DescribeDBInstances
- DescribeTimeWindow
- DescribeDBSwitchRecords
- DescribeDBZoneConfig
- ModifyAutoRenewFlag
- InitDBInstances
- IsolateDBInstance
- ModifyDBInstanceName
- ModifyInstanceTag
- ModifyRoGroupInfo
- ModifyNameOrDescByDpId
- ModifyDBInstanceProject
- ModifyTimeWindow
- ModifyDBInstanceVipVport
- OpenDBInstanceGTID
- OfflineIsolatedInstances
- OpenWanService
- ReleaseIsolatedDBInstances
- RestartDBInstances
- SwitchForUpgrade
- UpgradeDBInstance
- UpgradeDBInstanceEngineVersion
- Log APIs
- Rollback APIs
- Data Types
- Error Codes
- FAQs
- Reference
- Service Agreement
- Glossary
- Contact Us
- Release Notes
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Purchase Guide
- Get Started
- Operation Guide
- Best Practice
- Usage Specifications of TencentDB for MySQL
- Creating VPCs for TencentDB for MySQL
- Increase Business Load Capacity by MySQL Database
- Deploying Python Web Applications
- Build LAMP Stack for Web Application
- Build Drupal Website
- Configuring Application Automatic Reconnection
- Limits on Automatic Conversion from MyISAM to InnoDB
- Impact of Modifying MySQL Master Instance Parameters
- Call MySQL API by Python
- White Paper
- API Documents
- History
- Introduction
- API Category
- API Call Requests
- Task API
- Security API
- Database API
- Account API
- Monitoring APIs
- Parameter APIs
- Backup APIs
- Data Import APIs
- Instance APIs
- CreateRoInstanceIp
- BalanceRoGroupLoad
- AddTimeWindow
- CreateDeployGroup
- DescribeDBInstanceInfo
- DeleteDeployGroups
- DeleteTimeWindow
- CloseWanService
- DescribeRoMinScale
- DescribeRoGroups
- CreateDBInstanceHour
- DescribeDBInstanceCharset
- DescribeDBInstanceConfig
- DescribeDeployGroupList
- DescribeDBInstanceGTID
- DescribeDBInstanceRebootTime
- DescribeTagsOfInstanceIds
- DescribeDBInstances
- DescribeTimeWindow
- DescribeDBSwitchRecords
- DescribeDBZoneConfig
- ModifyAutoRenewFlag
- InitDBInstances
- IsolateDBInstance
- ModifyDBInstanceName
- ModifyInstanceTag
- ModifyRoGroupInfo
- ModifyNameOrDescByDpId
- ModifyDBInstanceProject
- ModifyTimeWindow
- ModifyDBInstanceVipVport
- OpenDBInstanceGTID
- OfflineIsolatedInstances
- OpenWanService
- ReleaseIsolatedDBInstances
- RestartDBInstances
- SwitchForUpgrade
- UpgradeDBInstance
- UpgradeDBInstanceEngineVersion
- Log APIs
- Rollback APIs
- Data Types
- Error Codes
- FAQs
- Reference
- Service Agreement
- Glossary
- Contact Us
TencentDB for MySQL supports four types of architectures: the High-availability Edition, the Finance Edition, the Single-node High IO Edition, and the Basic Edition. Currently, the Single-node High IO Edition applies to read-only instances only.
Viewing Instance Architectures
- For instances to be purchased, log in to the TencentDB for MySQL purchase page and select the architecture in the "Architecture" section.
- For purchased instances, log in to the MySQL console, locate the desired instance in the instance list, and view its architecture in the "Configuration" column.
Architecture Comparison
| Architecture | High-availability Edition | Finance Edition | Single-node High IO Edition | Basic Edition |
|---|---|---|---|---|
| Supported Version | MySQL v5.5, v5.6, v5.7, and v8.0 | MySQL v5.6, v5.7, and v8.0 | MySQL v5.6, v5.7, and v8.0 | MySQL v5.7 |
| Node | One source node, one replica node | One source node, two replica nodes | Single node | Single node |
| Source-replica Replication Mode | Async (default), semi-sync | Strong sync | - | - |
| Instance Availability | 99.95% | 99.99% | - | - |
| Underlying Storage | Local NVMe SSD | Local NVMe SSD | Local NVMe SSD | Premium cloud disk |
| Performance | Up to 240,000 IOPS | Up to 240,000 IOPS | - | The IOPS calculation formula: {min 1,500 + 8 * capacity, max 4,500} |
| Use Case | Gaming, internet, IoT, retail, e-commerce, logistics, insurance, securities, etc. | Gaming, internet, IoT, retail, e-commerce, logistics, insurance, securities, etc. | Applications with read/write separation requirements | Personal learning, small websites, non-core small enterprise systems, and medium-to-large enterprise development and testing |
Documentation
- TencentDB for MySQL supports MySQL v8.0, v5.7, v5.6, and v5.5. For more information, please see Database Version.
- TencentDB for MySQL supports the following instance types: the source instance, the read-only instance, and the disaster recovery instance. For more information, please see Database Instance Types.
- TencentDB for MySQL supports different features in different architectures. For more information, please see List of Feature Differences.
Was this page helpful?