Terms
The following terms are used in Cloud's MySQL product. To facilitate quick and easy use, we provide the following explanations:
Instance Types
MySQL instances include ordinary and high-availability instance types.
Ordinary instances provide a basic single-instance database. Ordinary MySQL instances provide a single database node, with data storage based on elastic block storage devices in a distributed storage architecture, separating computing and storage.
High-availability instances adopt a dual-master hot backup architecture, completely solving database unavailability caused by downtime or hardware failure. They support NVMe and SSD models, support high-availability deployment across availability zones, and achieve disaster recovery at the data center level.
Versions
MySQL instances currently support MySQL5.5, MySQL5.6, MySQL5.7, MySQL8.0, Percona 5.5, Percona5.6, and Percona 5.7, etc. Users can choose the corresponding cloud database version according to their needs.
Database Models
MySQL instances currently provide NVMe and SSD cloud disk models.
NVMe models can be well suited to various business scenarios. They use ultra-high-performance RDMA NVMe SSD cloud disks and support large-capacity (32T) storage with a high cost-performance ratio.
SSD cloud disk models are deployed in availability zones where NVMe models are not provided and can meet most business scenarios well. The underlying storage uses SSD cloud disks to effectively guarantee data security.
Memory
The memory size of the cloud database. Users can choose according to the hardware requirements of the cloud database.
Hard Disk
The hard disk size of the cloud database. Users can choose according to the hardware requirements of the cloud database.
Payment Method
The payment methods are divided into yearly, monthly, and on-demand. All payment methods are prepaid, that is, the cost of the corresponding service period is paid in advance.
For specific billing instructions, please refer to the "Purchase and Billing" document.
Quantity
The number of cloud databases that the user needs to apply for, the default is 1, and multiple can be selected for batch creation.
Master and Read-only instance
The master database supports read and write operations.
On the one hand, the Read-only database can serve as a disaster recovery node for the master database, and it can also support read operations to reduce the pressure on the master database and achieve read-write separation.
Configuration Files
Configuration files include various configuration parameters for the operation of the cloud database. Users can customize and modify them as needed. Default configuration files are provided for different versions of the cloud database.
Configuration files include default configuration files and custom configuration files. Custom configuration files are created and imported by users.
Administrator
Super administrator (root) privileges are provided by default, allowing users to customize the administrator password.
Instance Name
Users can customize the name of the cloud database instance.
Resource ID
After a user creates a cloud database instance, the system will automatically generate a Resource ID, which is globally unique.
IP and Port
The IP is the intranet address for users to access the cloud database. It is automatically generated after the cloud database is successfully created, and currently, no public IP is provided.
The default port for MySQL and Percona is 3306.
Backup
A backup saves all data from a cloud database at a certain point in time. The cloud database provides two ways of backup: automatic backup and manual backup, to prevent data loss and avoid risks from misoperations. The backup source can be chosen from the master or replication database, but backup from a replication database across availability zones is not currently supported.
Log
A log is a record file used to record cloud database operation events. It includes binary logs, slow query logs, error logs, and operation logs.
Service Level Agreement (SLA) for Cloud Database Service
The Service Level Agreement stipulates the general service level indicators and service precautions for providing cloud database services to customers. For details of the agreement, please click Service Level Agreement (SLA) for Cloud Database Service to view.
