- Release Notes
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Purchase Guide
- Get Started
- Operation Guide
- Best Practice
- Usage Specifications of TencentDB for MySQL
- Configuring Application Automatic Reconnection
- Impact of Modifying MySQL Master Instance Parameters
- Limits on Automatic Conversion from MyISAM to InnoDB
- Creating VPCs for TencentDB for MySQL
- Enhancing Business Load Capacity with TencentDB for MySQL
- Building LAMP Stack for Web Application
- Building Drupal Website
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Backup APIs
- Task APIs
- Security APIs
- Data Import APIs
- Parameter APIs
- Instance APIs
- DescribeDBInstanceGTID
- CloseWanService
- SwitchForUpgrade
- CreateDBInstanceHour
- DescribeDBInstanceCharset
- ModifyDBInstanceVipVport
- ModifyDBInstanceProject
- IsolateDBInstance
- UpgradeDBInstanceEngineVersion
- DescribeDBInstances
- InitDBInstances
- DescribeDBInstanceRebootTime
- OpenWanService
- UpgradeDBInstance
- ModifyDBInstanceName
- DescribeDBZoneConfig
- RestartDBInstances
- OpenDBInstanceGTID
- DescribeDBSwitchRecords
- DescribeDBInstanceConfig
- ModifyAutoRenewFlag
- ModifyInstanceTag
- DescribeTagsOfInstanceIds
- ModifyTimeWindow
- DescribeTimeWindow
- DeleteTimeWindow
- AddTimeWindow
- OfflineIsolatedInstances
- ReleaseIsolatedDBInstances
- ModifyRoGroupInfo
- DescribeRoGroups
- BalanceRoGroupLoad
- DescribeDBInstanceInfo
- DescribeRoMinScale
- CreateRoInstanceIp
- StopDelayReplication
- StartDelayReplication
- ModifyRoType
- ModifyRoReplicationDelay
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- ModifyNameOrDescByDpId
- Database APIs
- Account APIs
- Rollback APIs
- Monitoring APIs
- Log APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Notice
- Reference
- 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
- Configuring Application Automatic Reconnection
- Impact of Modifying MySQL Master Instance Parameters
- Limits on Automatic Conversion from MyISAM to InnoDB
- Creating VPCs for TencentDB for MySQL
- Enhancing Business Load Capacity with TencentDB for MySQL
- Building LAMP Stack for Web Application
- Building Drupal Website
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Backup APIs
- Task APIs
- Security APIs
- Data Import APIs
- Parameter APIs
- Instance APIs
- DescribeDBInstanceGTID
- CloseWanService
- SwitchForUpgrade
- CreateDBInstanceHour
- DescribeDBInstanceCharset
- ModifyDBInstanceVipVport
- ModifyDBInstanceProject
- IsolateDBInstance
- UpgradeDBInstanceEngineVersion
- DescribeDBInstances
- InitDBInstances
- DescribeDBInstanceRebootTime
- OpenWanService
- UpgradeDBInstance
- ModifyDBInstanceName
- DescribeDBZoneConfig
- RestartDBInstances
- OpenDBInstanceGTID
- DescribeDBSwitchRecords
- DescribeDBInstanceConfig
- ModifyAutoRenewFlag
- ModifyInstanceTag
- DescribeTagsOfInstanceIds
- ModifyTimeWindow
- DescribeTimeWindow
- DeleteTimeWindow
- AddTimeWindow
- OfflineIsolatedInstances
- ReleaseIsolatedDBInstances
- ModifyRoGroupInfo
- DescribeRoGroups
- BalanceRoGroupLoad
- DescribeDBInstanceInfo
- DescribeRoMinScale
- CreateRoInstanceIp
- StopDelayReplication
- StartDelayReplication
- ModifyRoType
- ModifyRoReplicationDelay
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- ModifyNameOrDescByDpId
- Database APIs
- Account APIs
- Rollback APIs
- Monitoring APIs
- Log APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Notice
- Reference
- Glossary
- Contact Us
TencentDB for MySQL supports three types of architectures: single-node (formerly Basic Edition), two-node (formerly High IO Edition), and three-node (formerly Finance Edition).
Note：
General single-node instances are formerly known as Single-node High IO Edition instances.
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 | Two-node | Three-node | Single-node | |
|---|---|---|---|---|
| Resource isolation policy | General | General | General | Basic |
| Supported version | MySQL 5.5, 5.6, 5.7, and 8.0 | MySQL 5.6, 5.7, and 8.0 | MySQL 5.6, 5.7, and 8.0 | MySQL 5.7 |
| Node | One source, one replica | One source, two replicas | Single node | Single node |
| Source-replica replication mode | Async (default), semi-sync | Async (default), strong sync, and semi-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 | - | IOPS calculation formula: {min 1,500 + 8 x disk capacity, max 4,500} |
| Use cases | 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 8.0, 5.7, 5.6, and 5.5. For more information, please see Database Versions.
- TencentDB for MySQL supports the following instance types: source instances and read-only replicas. 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.
Yes
No
Was this page helpful?