GaussDB(for MySQL)

GaussDB(for MySQL)

GaussDB(for MySQL) uses a decoupled compute and storage architecture and data functions virtualization (DFV) storage that auto-scales up to 128 TB per instance. There is virtually no risk of data loss. It supports millions of QPS and cross-AZ deployment, combining the performance and reliability of commercial databases with the flexibility of open source databases.

GaussDB(for MySQL) uses a decoupled compute and storage architecture and data functions virtualization (DFV) storage that auto-scales up to 128 TB per instance. There is virtually no risk of data loss. It supports millions of QPS and cross-AZ deployment, combining the performance and reliability of commercial databases with the flexibility of open source databases.

Why GaussDB(for MySQL)?

  • Robust Performance

    GaussDB(for MySQL) can deliver seven times the performance of open-source MySQL and achieve millions of queries per second (QPS).

    GaussDB(for MySQL) can deliver seven times the performance of open-source MySQL and achieve millions of queries per second (QPS).

  • Scalable

    You can add up to 15 read replicas within minutes, and also scale up or down vCPUs and memory of a GaussDB(for MySQL) instance to process uncertain workload growth.

    You can add up to 15 read replicas within minutes, and also scale up or down vCPUs and memory of a GaussDB(for MySQL) instance to process uncertain workload growth.

  • Reliable

    GaussDB(for MySQL) supports cross-AZ and remote disaster recovery for financial-grade reliability. There are three data copies to ensure data security.

    GaussDB(for MySQL) supports cross-AZ and remote disaster recovery for financial-grade reliability. There are three data copies to ensure data security.

  • Cost-effective

    The cost of GaussDB(for MySQL) is only 10% of a commercial database.

    The cost of GaussDB(for MySQL) is only 10% of a commercial database.

  • Compatible

    GaussDB(for MySQL) is fully compatible with MySQL, so there is no need to re-architect applications.

    GaussDB(for MySQL) is fully compatible with MySQL, so there is no need to re-architect applications.

  • Middleware-free

    Distributed Database Middleware (DDM) is not required for sharding.

    Distributed Database Middleware (DDM) is not required for sharding.

Activities & Promotions Activities

Free Packages

Register now to take advantage of these incredible deals

Hot
Try Now
Huawei Cloud Blossom Program

Help your business bloom with cloud resource discounts, free trainings, and collaborative marketing opportunities

Try Now

GaussDB(for MySQL) Billing

You only pay for what you use. There is no minimum charge.

GaussDB(for MySQL) provides two billing modes:

· 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.

Renewing/Unsubscribing a GaussDB(for MySQL) Instance

Only yearly/monthly instances of GaussDB(for MySQL) can be renewed or unsubscribed.

To renew an instance, you can open the Instances page, locate the instance and click Renew in the Operation column.

To unsubscribe an instance, you need to unsubscribe the order first. After you unsubscribe the instance order, all resources including read replicas of the instance are also deleted.

Changing the Billing Mode from Yearly/Monthly to Pay-per-Use

You can change the billing mode of a GaussDB(for MySQL) instance from yearly/monthly to pay-per-use. The pay-per-use billing mode takes effect only after the yearly/monthly subscription expires, and the auto-renew function will be invalid.

Changing the Billing Mode from Pay-per-Use to Yearly/Monthly

If you use GaussDB(for MySQL) for a long time, you can change the billing mode of one or multiple instances from pay-per-use to yearly/monthly for a lower tariff. After the change, you can check whether the operation has taken effect in the order status.

FAQs

  • Does GaussDB(for MySQL) Support Automatic Failover?

    Yes. During the creation of a GaussDB(for MySQL) instance, a primary node and a read replica are both created. If the primary node fails, the read replica is automatically promoted to the primary node to provide services, and the original primary node is demoted to be a read replica.

  • Does GaussDB(for MySQL) Support Decoupling of Compute and Storage?

    GaussDB(for MySQL) supports the decoupling of compute and storage, improving high availability and the experience in backup and restoration, upgrade and capacity expansion.

  • What Types of DB Engines Does GaussDB(for MySQL) Support for Importing Data?

    · Exporting or importing data between DB engines of the same type is called homogeneous database export or import.

    · Exporting or importing data between DB engines of different types is called heterogeneous database export or import. For example, import data from Oracle to the DB engines supported by GaussDB(for MySQL).

    · Generally, data cannot be exported or imported between heterogeneous databases due to the different data formats involved. However, if the data formats are compatible, table data can, in theory, be migrated between them.

    · Third-party software is usually required for data replication to export and import between heterogeneous databases. For example, you can use a third-party tool to export table records from Oracle in .txt format. Then, you can use Load statements to import the exported table records to the DB engines supported by GaussDB(for MySQL).

  • How Can I Install the MySQL Client?

    MySQL provides client installation packages for different OSs on its official website. Download the MySQL 8.0 client installation package or packages of other versions. The following uses Red Hat Linux as an example to show how to obtain the required installation package and install it.

  • Can I Access a GaussDB(for MySQL) Instance over an Intranet Connection Across Regions?

    By default, instances cannot be accessed over an intranet across regions. Cloud services in different regions cannot communicate with each other over an intranet. You can use Cloud Connect (CC) or Virtual Private Network (VPN) to connect to instances across regions.

    · CC allows you to connect two VPCs of the same account or different accounts even if they are in different regions. For details, see Communication Among VPCs of the Same Account.

    · VPN uses an encrypted tunnel to connect VPCs in different regions and sends traffic over the Internet. It is inexpensive, easy to configure, and easy to use. However, the quality of VPN connections depends on the quality of Internet connections. For details, see Connecting an On-Premises Data Center to a VPC Through a VPN.

  • What Should I Pay Attention to When Using GaussDB(for MySQL)?

    · Instance operating systems (OSs) are invisible to you. Your applications can access a database only through an IP address and a port.

    · The backup files stored in Object Storage Service (OBS) buckets and the Elastic Cloud Servers (ECSs) used by GaussDB(for MySQL) are invisible to you. They are visible only to the instance management system.

    · When you view your instance in the instance list, select the region where your instance is located.

    · Precautions after GaussDB(for MySQL) instances are created:

    After your instance is created, you do not need to perform basic database O&M operations, such as applying HA and security patches, but you must pay attention to:

    a. vCPUs and memory of your instance. If they become insufficient, you need to change them in a timely manner.

    b. Storage space of your instance. If the storage is used up, you will be billed on a pay-per-use basis for any additional storage, but if you scale up storage in advance, you can pay for the additional storage at yearly/monthly rates.

    c. Performance of your instance. You need to check for slow query SQL statements, SQL statements to be optimized, or redundant or missing indexes regularly.