Function Overview

MySQL is one of the world's most popular open-source relational databases. It works with the Linux, Apache, and Perl/PHP/Python to establish a LAMP model for efficient web solutions. RDS for MySQL is reliable, secure, scalable, inexpensive, easy to manage, and immediately ready for use.

• It uses a stable architecture and supports various web applications. In addition, it is cost-effective and is preferred by small- and medium-sized enterprises.
• A web-based console is available for you to monitor comprehensive information, making operations easy and visual.
• Resources can be flexibly scaled and you pay for only what you use.

RDS provides yearly/monthly and pay-per-user billing options to help optimize costs.

• Yearly/monthly provides a larger discount than pay-per-use billing and is recommended for long-term use.
  
• Pay-per-use (hourly) allows you to pay for only the resources you actually use. Less than one hour will be calculated as one full hour.
• You can change the billing mode of an instance from yearly/monthly to pay-per-use, or from pay-per-use to yearly/monthly.
  

RDS for MySQL offers various migration methods:

• Migrate data using DRS
• Migrate data using mysqldump

Among these migration methods, DRS is recommended because it is stable, efficient, easy to use, and simplifies the complexity of data transmission and reduces the transmission costs.

You can reset the password of your database account when using RDS. If an exception occurs on the root account, for example, the root account is lost or deleted, you can reset the root password to restore the account rights.

You can bind an EIP to a DB instance for public accessibility and can also unbind the EIP from the DB instance as needed.

• You can bind an EIP to a primary DB instance or a read replica only.
• If a DB instance has already an EIP bound, you must unbind the EIP from the DB instance first before binding a new one to it.
  

In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. To offload read pressure on the database, you can create read replicas in a region. These read replicas can process a large number of read requests and increase application throughput.

You can scale up storage space if it is no longer sufficient for your requirements. If the DB instance status is Storage full and data cannot be written to databases, you need to scale up storage space. Services are not interrupted during storage scale-up.

You can change the DB instance class of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the change is successful.

RDS for MySQL supports the following restoration methods:

• Instance-level restoration: Automated or manual backups can be used to restore the entire DB instance.
• Database- or table-level restoration: Automated backups can be used to restore databases or tables to a point in time.
• Cross-region restoration: If a DB instance in one region fails, you can use backups stored in another region to restore data to a new DB instance.

You can use database parameter templates to manage DB engine configurations. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.

When creating a DB instance, you can use a default parameter template or create a custom template. After the DB instance is created, you can change the applied parameter template.

• Default parameter template

      DB engine defaults and database system defaults are included in default parameter templates.

• Custom parameter template

      If you want to use your custom parameter settings, you can create a parameter template and apply it with your DB instance.

Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. You can enable read/write splitting after read replicas are created. Write requests are automatically routed to the primary DB instance and read requests are routed to read replicas or the primary DB instance by user-defined weights.

DBA Assistant provides you with a range of database O&M functions, making it easy to diagnose database problems, locate faults, analyze and optimize database performance.

• Error logs contain logs generated while a DB instance is running. They can help you analyze database problems.
• Slow query logs record statements that exceed long_query_time (1s by default). You can view log details and statistics to identify statements that are executing slowly and need to be optimized.
• Failover/switchover logs help you evaluate the impact of primary/standby switchovers on your workloads.
• SQL Audit records all SQL operations in log files for download and query.

RDS supports v3 APIs. You can invoke RDS APIs to perform a range of operations, such as DB instance creation and deletion, backup and restoration, and parameter query and modifications.

With RDS SDKs, you can easily invoke RDS APIs to create applications on Huawei Cloud. Currently, SDKs support Java, Python, and Go languages.