Function Overview

GaussDB(for MySQL) is a MySQL-compatible, enterprise-class distributed database service. Data functions virtualization (DFV) is used to decouple storage from compute, a DB instance can auto scale up to 128 TB, and a failover can be performed within seconds. It provides the superior performance of a commercial database at the price of an open-source database.

• By decoupling compute and storage and using a "log as database" architecture, GaussDB(for MySQL) delivers seven times the performance of open-source MySQL.
• Up to 15 read replicas can be added to a primary node to handle high-concurrency requests.
• DB instance can be deployed across three AZs or across regions to improve DR capabilities.
• GaussDB(for MySQL) is fully compatible with MySQL. You can easily migrate your MySQL databases to GaussDB(for MySQL) without refactoring existing applications.

GaussDB(for MySQL) provides yearly/monthly and pay-per-user billing options to help optimized 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. Pricing is listed on a per-hour basis, but bills are calculated down to the second.
• You can change the billing mode of an instance from yearly/monthly to pay-per-use, or from pay-per-use to yearly/monthly.

You can connect your instances over a private network, a public network, or using Data Admin Service (DAS).

You can configure security group rules to allow specific IP addresses to access your instances. The default security group rule allows all outgoing data packets and allows ECSs and GaussDB(for MySQL) instances in the same security group to access each other by default. You can then define different access control rules for a security group, and these rules take effect for all instances added to this security group.

You can bind an EIP to an instance to enable public network access and can unbind the EIP later if needed.

You can migrate data to GaussDB(for MySQL) instances using DRS or mysqldump.

If you forget the password of your database account when using GaussDB(for MySQL), you can reset the password.

If there is a problem with the root account, for example, if your root account credentials are lost or deleted, you reset the root password to restore access.

You cannot reset the password if:

• Your account is frozen.
• The database port is being changed.
• The instance status is Creating, Restoring, Rebooting, Changing port, Changing instance specifications, Promoting to primary, or Abnormal.

You can change vCPUs and memory of an instance if needed.

If the status of an instance changes from Changing instance specifications to Available, the change is successful.

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 instances are created. Write requests are automatically routed to the primary node and read requests are routed to read replicas and the primary node by user-defined weights. Currently, you can create up to four proxy instances to isolate complex services. You can use the corresponding connection address to connect to a proxy instance.

In read-intensive scenarios, a primary node may be unable to handle the read pressure and services may be affected. To offload read pressure from the primary node, you can create one or more read replicas in the same region as the primary node. These read replicas can process a large number of read requests and increase application throughput.

GaussDB(for MySQL) lets you back up and restore your instances to ensure data reliability. You can restore data to:

• A new DB instance, the original DB instance, or an existing DB instance using an automated or manual backup.
• A specified point in time. It is instance-level data restoration. Data can be resorted to a new DB instance, the original DB instance, or an existing 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 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 own parameter settings, you can create a custom parameter template and apply it to your DB instance.

You can view error logs and slow query logs on the GaussDB(for MySQL) console.

• Error logs contain logs generated during the database running. They can help you analyze database problems.
• Slow query logs record statements that exceed long_query_time. You can view log details and statistics to identify statements that are executing slowly and need to be optimized.

You can invoke APIs to perform a range of operations, such as instance creation and deletion, backups and restorations, and parameter query and modifications.