Before using TencentDB for MySQL, you need to consider the following two questions:
You don't need to care about the daily maintenance and adjustment of MySQL, which is taken care of by the OPS system of TencentDB.
In case of an exception with MySQL, the OPS system can identify it and notify the OPS personnel immediately, and you don't need to make any changes.
No, because the standards for splitting databases and tables are subject to your specific business logic.
The capacity actually used by your data and the capacity occupied by log data such as binlogs are calculated separately. The occupied capacity displayed in the TencentDB for MySQL Console equals the used capacity.
If multiple SQL statements are sent to TencentDB for execution within a very short period of time, will TencentDB for MySQL run them one by one or crash? What is the maximum number of allowed concurrent connections?
A TencentDB for MySQL instance works in the same way as a self-built MySQL instance. Whether concurrently executed statements will cause a crash depends on system resources and SQL statements themselves.
When the number of connections reaches the upper limit (max_connections), the instance will basically not able to provide services properly. This is generally caused by the following reasons:
For specific precautions, see Use Limits.
Instead of providing external access, the default standby database is primarily used for high-availability switchover.
For the sake of database security (for example, when the master instance fails, you can quickly switch to the slave database), TencentDB for MySQL doesn't allow you to read from or write to the slave database.
If greater read/write capability is desired, you can consider upgrading the instance configuration or purchasing a read-only instance.
Region change is not supported for the time being. You can use DTS to migrate data between instances in different regions. DTS supports real-time data sync. After data migration is completed, the source instance can be returned in a self-service manner.
After termination, a monthly subscribed instance will be retained in the recycle bin for 7 days, and a pay-as-you-go instance for 1 day. During the retention period, terminated instances can be recovered from the recycle bin.
You can use MySQL v5.5 which supports MyISAM. Even so, you are recommended to choose a higher version like MySQL v5.7, as the InnoDB engine can provide finer-grained row-level locking, deliver a higher write performance, guarantee data integrity, and avoid data loss in case of database failure.
Cross-region access is unavailable in VPC by default, as VPCs in different regions are isolated from each other. You are recommended to purchase TencentDB for MySQL instance in the same region as your CVM instances, so that local access can be enabled for data, which guarantees high service speed and stability.