TencentDB for MySQL supports three types of architectures: single-node, two-node, and three-node. This document describes the single-node architecture.
Single-node instances support two resource isolation policies: basic and general. Basic single-node instances are formerly known as the Basic Edition, and read-only replicas adopt the general single-node architecture. For more information, please see Resource Isolation Policy.
We do not recommend basic single-node instances for the business production environment. It is more suitable for personal learning, small websites, non-core small enterprise systems, and medium-to-large enterprise development and testing.
As it adopts a single-node architecture, when the node fails, it takes slightly longer to recover than CVM (due to instance startup and data restoration). If your business requires high availability, we recommend you use two-node or three-node MySQL instances.
Currently, it is ideal only for read-only replicas in various industries with read/write separation requirements.
It uses local NVMe SSD disks for underlying storage with excellent IO performance and is ideal for read-only instances to share business read load.
- Single-node deployment is susceptible to single points of failure. If only one read-only replica is purchased, it is impossible to ensure high availability for your business, because a failure of the single read-only replica will lead to business disruption.
- As the time taken to recover a single read-only replica depends on the business data volume, the recovery time cannot be guaranteed. As a result, if your business requires high availability, we recommend you purchase at least two read-only replicas for the RO group.