HUAWEI GaussDB Service Overview

Download

GaussDB(for MySQL)

Service Overview

Issue 01

Date 2020-10-27

HUAWEI TECHNOLOGIES CO., LTD.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specied in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every eort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: https://www.huawei.com

Email: support@huawei.com

GaussDB(for MySQL) Service Overview Contents

1 What Is GaussDB(for MySQL)?.............................................................................................1

2 Product Architecture............................................................................................................... 2

3 Basic Concepts.......................................................................................................................... 4

4 Product

Benets.......................................................................................................................5

5 DB Instance Description......................................................................................................... 7

5.1 DB Instance Classes................................................................................................................................................................ 7

5.2 DB Engines and Versions...................................................................................................................................................... 7

5.3 DB Instance Statuses.............................................................................................................................................................. 8

6 Constraints................................................................................................................................ 9

7 Billing....................................................................................................................................... 11

8 Related Services.....................................................................................................................13

A Change History...................................................................................................................... 14

GaussDB(for MySQL) Service Overview 1 What Is GaussDB(for MySQL)?

1 What Is GaussDB(for MySQL)?

GaussDB(for MySQL) is an enterprise-class distributed database and fully compatible with MySQL. It uses a decoupled compute and storage architecture and supports up to 128 TB of storage. With GaussDB(for MySQL), there is no need to deal with sharding, and no need to worry about data loss. It combines the performance and availability of commercial databases with the of open source databases.

cost-eectiveness

5.2 DB Engines and Versions lists the versions supported by GaussDB(for

MySQL).

Using GaussDB(for MySQL)

You can use GaussDB(for MySQL) in the following ways:

Management console: You can create and manage GaussDB(for MySQL) DB instances on the web-based management console.

To help you better use GaussDB(for MySQL), see 1 What Is GaussDB(for

MySQL)? and 3 Basic Concepts.

GaussDB(for MySQL) Service Overview 2 Product Architecture

2 Product Architecture

The overall architecture of GaussDB(for MySQL) consists of three layers from bottom to top.

1. Storage node layer: This layer uses DFV storage to provide distributed, strongconsistency, and high-performance storage capabilities to ensure data reliability and horizontal scalability.

2. Storage abstraction layer: This layer is key to ensuring database performance. It connects to the DFV storage pool downward and provides scheduled database storage semantics upward. Table le-based operations are abstracted into distributed storage.

3. SQL node layer: This layer reuses MySQL 8.0 code to be 100% compatible with open-source MySQL. You do not need to modify any code when migrating your services from MySQL or other databases to GaussDB(for MySQL). The MySQL-native syntax and tools are still available, reducing your development and learning costs. Apart from full compatibility, GaussDB(for MySQL) also optimizes the kernel, open-source hardening, open-source ecosystem, and commercial capabilities based on native MySQL.

eciently

GaussDB(for MySQL) Service Overview 2 Product Architecture

GaussDB(for MySQL) Service Overview 3 Basic Concepts

3 Basic Concepts

Understanding the following concepts helps you better use GaussDB(for MySQL):

● Primary/standby: GaussDB(for MySQL) uses a decoupled compute and storage architecture that auto-scales up to 128 TB per DB instance. A primary/standby DB instance contains a primary node and up to 15 read replicas which can be created in minutes.

● Region: A region is a physical data center. Generally, GaussDB(for MySQL) DB instances and ECSs must be located in the same region for high access performance.

● Availability zone (AZ): An AZ contains one or multiple physical data centers. Each AZ has independent cooling, electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple instances. An AZ is a geographic location with independent power supply and network facilities in a region.

AZs are physically isolated but interconnected over an intranet. Each AZ provides unaected by faults in other AZs. As a result, provisioning GaussDB(for MySQL) DB instances in separate AZs protect your applications against local faults that occur in a single location. AZs within the same region have no functional

● Instance class: resource conguration of each node, for example, 16 vCPUs and 64 GB.

cost-eective and low-latency network connections that are

dierences.

re extinguishing, moisture-proof, and

GaussDB(for MySQL) Service Overview 4 Product Benets

4 Product Benets

GaussDB(for MySQL) is an enterprise-class cloud database that uses a decoupled compute and storage architecture.

Requirements and Pain Points

Table 4-1 Requirements and pain points

Requirements and Pain Points

MySQL compatibility

Mass storage Large data storage capacity for Internet services

Distributed scalability

Strong-consistency transactions

High availability Multi-AZ high availability and multi-region disaster

High concurrency High performance in high concurrency scenarios

Non-middleware architecture

Description

For primary/standby DB instances, no need to reconstruct original MySQL applications

Automatic sharding or non-sharding with no impact on services

Strong consistency of distributed transactions

recovery

No need to work with distributed database middleware for sharding

Core Advantages

Table 4-2 Core advantages

Advantage

Superior performance Million-level QPS

Description

GaussDB(for MySQL) Service Overview 4 Product Benets

Advantage Description

High scalability 1 primary node and up to 15 read replicas; 128 TB

storage space

High reliability Cross-AZ deployment and three data copies

High compatibility Compatible with MySQL

Ultra-low cost On par with commercial databases at 1/10 the cost.

Customer

Benets

● Mass storage with 128 TB capacity and no sharding required

● Easy-to-use, fully compatible with MySQL, and no application reconstruction required

● Up to 15 read replicas and read/write splitting available for a primary/standby DB instance

● Multi-AZ deployment, remote disaster recovery, and high reliability

GaussDB(for MySQL) Service Overview 5 DB Instance Description

5 DB Instance Description

5.1 DB Instance Classes

5.2 DB Engines and Versions

5.3 DB Instance Statuses

5.1 DB Instance Classes

GaussDB(for MySQL) instance classes are listed in the following table and vary according to actual situations.

Table 5-1 Instance classes

Instance Class

Generalenhanced

Kunpeng generalenhanced

vCPUs Memory (GB)

16 64

32 128

60 256

16 64

32 128

48 192

5.2 DB Engines and Versions

Table 5-2 lists the DB engines and versions supported by GaussDB(for MySQL).

GaussDB(for MySQL) Service Overview 5 DB Instance Description

Table 5-2 DB engines and versions

DB Engine DB Engine Version

GaussDB(for MySQL) MySQL 8.0

5.3 DB Instance Statuses

DB Instance Statuses

The status of a DB instance indicates the health of the instance. You can view the DB instance status on the management console.

Table 5-3 DB instance statuses

Status Description

Available DB instance is available.

Abnormal DB instance is abnormal.

Creating DB instance or backup is being created.

Creation failed DB instance failed to be created.

Rebooting DB instance is being rebooted.

Changing port DB instance port is being changed.

Changing instance class

Promoting to primary

Scaling up Storage space of a DB instance is scaling up.

Frozen DB instance is frozen when the account balance is less than

Deleted DB instance has been deleted and will not be displayed in the

CPU or memory of a DB instance is being changed.

A read replica is being promoted to the primary node.

or equal to $0 USD. Retained frozen DB instances are unfrozen only after your account is recharged and the overdue payments are cleared.

instance list.

GaussDB(for MySQL) Service Overview 6 Constraints

6 Constraints

Table 6-1 shows the constraints designed to ensure the stability and security of

GaussDB(for MySQL).

Table 6-1 Function constraints

Function Constraints

GaussDB(for MySQL) access

Deployment ECSs in which GaussDB(for MySQL) DB instances are

Database root permissions

Database parameter

modication

● If GaussDB(for MySQL) DB instances are not bound with EIPs, the DB instances must be in the same VPC subnet as the ECSs associated with these instances.

● Security group rules must be added to allow ECSs to access GaussDB(for MySQL) DB instances. By default, a GaussDB(for MySQL) DB instance cannot be accessed by an ECS in a it, you must add an inbound rule to the GaussDB(for MySQL) security group.

● The default GaussDB(for MySQL) port:

– For primary/standby DB instances, the default port is

3306. You can change it if you want to access GaussDB(for MySQL) through another port.

deployed are not visible to users. You can access GaussDB(for MySQL) DB instances only over an IP address and a port.

The instance creation page provides only the root user permissions.

Most parameters can be modied on the GaussDB(for MySQL) console.

dierent security group. To allow

Data migration DRS or mysqldump is used to migrate data to GaussDB(for

MySQL).

GaussDB(for MySQL) Service Overview 6 Constraints

Function Constraints

MySQL storage engine

GaussDB(for MySQL) instance reboot

GaussDB(for MySQL) backup

les

GaussDB(for MySQL) is fully compatible with MySQL. Therefore, the supported storage engines are the same as those supported by MySQL.

For details, see What Storage Engines Does the RDS for

MySQL Support?

GaussDB(for MySQL) DB instances must be rebooted on the GaussDB(for MySQL) console.

GaussDB(for MySQL) backup les are stored in OBS buckets and are not visible to users.

GaussDB(for MySQL) Service Overview 7 Billing

7 Billing

GaussDB(for MySQL) allows you to pay only for what you use. There is no minimum fee.

Billing Item

GaussDB(for MySQL) charges you for your DB instances, database storage, and backup storage (optional).

Table 7-1 Billing items

Billing Item

Instance class DB instance class (CPU and memory) is billed on the yearly/

Database storage

Backup storage (optional)

Public network

trac

Description

monthly or pay-per-use basis.

Storage space that you have provisioned to your DB instance is billed on the yearly/monthly or pay-per-use basis.

GaussDB(for MySQL) provides backup storage up to 100% of your provisioned database storage at no additional charge. If the backup storage usage exceeds 100% of your provisioned database storage, tiered pricing starts.

GaussDB(for MySQL) DB instances are accessible from both private and public networks. Only the trac from public networks is billed.

Billing Modes

GaussDB(for MySQL) provides the following two billing modes:

● Yearly/Monthly: Provides a larger discount than pay-per-use mode and is recommended for long-term users.

● Pay-per-use (hourly): Allows you to pay for only the resources you have used.

exible billing mode and the minimum time unit is one hour. Partial

It is a hours are billed as full hours.

GaussDB(for MySQL) Service Overview 7 Billing

The billing mode of DB instances can be changed from pay-per-use to yearly/ monthly. For details, see Changing the Billing Mode from Pay-per-Use to

Yearly/Monthly.

Changing Instance Specication

● Modifying DB instance specications: You can modify GaussDB(for MySQL) DB instance modication, you are charged based on the new instance specications.

● Scaling up storage space: You can change the storage space of primary/ standby instances based on service requirements. After scaling the storage space, you will be charged based on the new storage space. Storage space can only be scaled up, not down. The minimum increment for each scaling is 10 GB.

specications based on service requirements. After the

GaussDB(for MySQL) Service Overview 8 Related Services

8 Related Services

The following gure shows the relationship between GaussDB(for MySQL) and other services.

Table 8-1 Related services

Service Name Description

Elastic Cloud Service (ECS)

Virtual Private Cloud (VPC)

Object Storage Service (OBS)

Cloud Eye Acts as an open monitoring platform that monitors

Cloud Trace Service (CTS)

Data Replication Service (DRS)

Enterprise Project Management Service (EPS)

Enables you to access GaussDB(for MySQL) DB instances through an ECS to reduce application response time and public network trac fees.

Isolates your networks and controls access to your GaussDB(for MySQL) DB instances.

Stores automated and manual backups of your GaussDB(for MySQL) DB instances.

GaussDB(for MySQL) resources in real time. It reports alarms and issues warnings promptly to ensure that services are running properly.

Provides records of operations on cloud service resources, enabling you to query, audit, and backtrack operations.

Smoothly migrates databases to the cloud.

Allows you to manage cloud resources and user groups by enterprise project.

Tag Management Service (TMS)

Provides visualized service for fast and unied cross-region tagging and categorization of cloud services.

GaussDB(for MySQL) Service Overview A Change History

A Change History

Released On Description

2020-10-27 This issue is the rst ocial release.

HUAWEI GaussDB Service Overview

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

1 What Is GaussDB(for MySQL)?

2 Product Architecture

3 Basic Concepts

5 DB Instance Description

5.1 DB Instance Classes

5.2 DB Engines and Versions

5.3 DB Instance Statuses

6 Constraints

7 Billing

8 Related Services

A Change History