Database Instance Types

Recent Pages

Last updated: 2022-01-19 15:04:23

A TencentDB for MySQL instance is a database environment that runs independently in Tencent Cloud. It is the basic unit for you to purchase the TencentDB for MySQL service. You can create, modify, and delete instances in the console.
Each instance is independent of each other with isolated resources. There are no CPU, memory, and IO preemption issues between instances. Each instance has its own characteristics such as database type and version, and the system has corresponding parameters to control instance behaviors.

There are three types of instances available in TencentDB for MySQL:

Instance Type	Definition	Architecture	Visible in Instance List	Feature
Source instance	An instance that can be read from and written to	Single-Node Two-Node Three-Node	Yes	A source instance can mount read-only instances and disaster recovery instances for read/write separation and remote disaster recovery
Read-Only instance	An instance that can only be read from	Single-Node	Yes	A read-only instance cannot exist on its own. Instead, it must be affiliated to a source instance. Its data comes solely from syncing with the source instance, and it must reside in the same region as the source instance
Disaster recovery instance	An instance that supports disaster recovery across AZs and regions	Two-Node	Yes	A disaster recovery instance is read-only when it syncs with a source instance. It can actively stop the sync and be promoted to a source instance for read/write access. The disaster recovery instance should reside in a different region than the source instance does

Reference

For more information on the creation of and notes on the read-only instance, see Creating Read-Only Instance.
For more information on how to create and configure RO groups for read-only instances, see RO Group of Read-Only Instances.
For more information on the creation of and notes on the disaster recovery instance, see Disaster Recovery Instance.

Recent Pages