TencentDB for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Database Architecture
- Database Instance
- Kernel Features
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Parallel Query
- Security Features
- Stability Features
- Purchase Guide
- Getting Started
- Connecting to MySQL Instance
- Database Audit
- Audit Rule Template
- MySQL Cluster Edition
- Maintenance Management Instance
- Operation Guide
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Database Proxy Kernel Features
- Database Proxy Management
- Automatic Read/Write Separation Feature
- Connection Pool Feature
- Other Features
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Restoring Database from Backup File
- Monitoring and Alarms
- Operation Logs
- Practical Tutorial
- Calling MySQL APIs in Python
- White Paper
- Performance White Paper
- Performance Test Report
- Troubleshooting
- Connections
- API Documentation
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- Database Proxy APIs
- Database Audit APIs
- Security APIs
- Account APIs
- Backup APIs
- Database APIs
- Monitoring APIs
- Log-related API
- FAQs
- Backup
- Connection and Login
- Instance Upgrade
- Performance and Memory
- Service Agreement
- Reference
Overview
Last updated: 2024-11-21 10:55:22
TencentDB for MySQL supports four types of architectures: single-node (cloud disk edition), two-node (formerly high availability edition), and three-node (formerly finance edition),Cluster Edition (cloud disk edition).
Note:
The single-node (cloud disk edition) architecture is currently available in the regions of Shanghai, Beijing, Guangzhou, Chengdu, Hong Kong of China, Singapore, and Frankfurt. Other regions will be available gradually in the future.
The two-node (formerly high availability edition) employs a one-primary-one-replica mode. Only the primary database provides access services, and the replica database is dedicated for disaster recovery without providing access.
The three-node (formerly finance edition) employs a one-primary-two-replica mode. Only the primary database provides access services, and the two replica databases are dedicated for disaster recovery without providing access.
The Cluster Edition (cloud disk edition) employs a one-primary-multiple-replica mode. The primary node (read-write node) provides read-write services, and the replica nodes (read-only nodes) provide read-only access services.
Viewing the instance architecture
For instances to be purchased, enter the TencentDB for MySQL purchase page, and select the architecture in the Architecture section.
For purchased instances, log in to the TencentDB for MySQL console, find the target instance from the instance list, and view its architecture in the Configuration Info section.
Architecture comparison
Architecture | Cluster Edition | Two-Node | Three-Node | Single-Node | |
Standard, Enhanced | General | General | General (Read-Only Instance) | Basic Type | |
Supported Versions | MySQL 5.7, 8.0 | MySQL 5.5, 5.6, 5.7, 8.0 | MySQL 5.6, 5.7, 8.0 | MySQL 5.6, 5.7, 8.0 | MySQL 5.7, 8.0 |
Node | One-Primary-Multiple-Replica (Up to 5 Read-Only Nodes) | One-Primary-One-Replica | One-Primary-Two-Replica | Single Node | Single Node |
Primary-Replica Replication Mode | Asynchronous/Semi-Synchronous (Default) | Asynchronous (Default), Semi-Synchronous | Asynchronous (Default), Fully Synchronous, Semi-Synchronous | - | - |
Instance Availability | 99.95% | 99.95% | 99.99% | - | - |
Underlying Storage | Tremendous SSD Cloud Disk Enhanced SSD Cloud Disk SSD Cloud Disk | Local NVMe SSD Disk | Local NVMe SSD Disk | Local NVMe SSD Disk | Enhanced SSD Cloud Disk SSD Cloud Disk |
IOPS Performance | Tremendous SSD Cloud Disk Benchmark Performance : Random IOPS = min{4000+Capacity(GiB)×100, 50000} Enhanced SSD Cloud Diske Benchmark Performance : Random IOPS = min{1800+Capacity(GiB)×50, 50000} SSD Cloud Disk Random IOPS = min{1800+Capacity(GiB)×30, 26000} | Up to 240,000 IOPS | Up to 240,000 IOPS | Up to 240,000 IOPS | Enhanced SSD Cloud Disk Benchmark Performance : Random IOPS = min{1800+Capacity(GiB)×50, 50000} SSD Cloud Disk Random IOPS = min{1800+Capacity(GiB)×30, 26000} |
Throughput Performance (MB/s) | Tremendous SSD Cloud Disk Benchmark Performance : Throughput = min{120+Capacity(GiB)×0.5, 350} Enhanced SSD Cloud Disk Benchmark Performance : Throughput = min{120+Capacity(GiB)×0.5, 350} SSD Cloud Disk Throughput = min{120+Capacity(GiB)×0.2, 260} | - | - | - | Enhanced SSD Cloud Disk Benchmark Performance : Throughput = min{120+Capacity(GiB)×0.5, 350} SSD Cloud Disk Throughput = min{120+Capacity(GiB)×0.2, 260} |
Applicable Scenarios | Applications in various industries such as gaming, the internet, Internet of Things, retail and e-commerce, logistics, insurance, and securities. | Applications in various industries such as gaming, the internet, Internet of Things, retail and e-commerce, logistics, insurance, and securities. | Applications in various industries such as gaming, the internet, Internet of Things, retail and e-commerce, logistics, insurance, and securities. | Applications with Read/Write Separation Requirements | Personal learning, small websites, non-core small enterprise systems, and medium-to-large enterprise development and testing environments. |
References
TencentDB for MySQL supports MySQL 5.5, 5.6, 5.7, and 8.0. For more information, see Database Versions.
TencentDB for MySQL supports the following instance types: the source instance, the read-only instance, and the disaster recovery instance. For more information, see Database Instance Types.
TencentDB for MySQL supports different features in different architectures. For more information, see List of Feature Differences.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No