Introduction to GaussDB(for MySQL)
Product Architecture
The GaussDB(for MySQL) architecture consists of three layers. From bottom to top, they are:
· Storage node layer. Data functions virtualization (DFV) storage provides distributed, strong-consistency, and high-performance storage, featuring high data reliability and excellent horizontal scalability. The data reliability is no less than 99.999999999% (11 nines). DFV is a solution for a data-centric full-stack service architecture with decoupled storage and compute.
· Storage abstraction layer. This layer is key to ensuring database performance. It connects to the DFV storage pool below it and provides semantics upward for ensuring efficient storage scheduling. Table file operations are abstracted into distributed storage.
· SQL parsing layer: 100% compatible with open-source MySQL 8.0. You can use MySQL-native syntax and tools to migrate your workloads from MySQL to GaussDB(for MySQL), saving your time and efforts. In addition to full compatibility with MySQL, GaussDB(for MySQL) comes with an optimized kernel and a hardened system. It is part of an open ecosystem and provides commercial capabilities of native MySQL.
Basic Concepts
Before using GaussDB(for MySQL), you should be familiar with the following concepts.
· Primary/standby instances: GaussDB(for MySQL) has an architecture with decoupled storage and compute that auto-scales up to 128 TB per instance. A primary/standby instance can contain a primary node and up to 15 read replicas which can be created in minutes.
· Regions are defined by a combination of geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region. Regions can be universal or dedicated. A universal region provides all sorts of cloud services for all users. A dedicated region provides only services of a given type or only for specific users. Generally, GaussDB(for MySQL) 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, fire extinguishing, moisture-proofing, and electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into 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 cost-effective and low-latency network connections that are unaffected by faults in other AZs. As a result, provisioning GaussDB(for MySQL) instances in separate AZs protects your applications against local faults that occur in a single location. AZs within the same region have no functional differences.
· Instance specifications: Each instance is configured with compute and memory resources, for example, 16 vCPUs and 64 GB.
· Compatibility between GaussDB(for MySQL) and browsers: See Which Browsers Are Supported?
Supported DB Engines and Versions
|
DB Engine
|
Version
|
Minor Kernel Version
|
|---|---|---|
GaussDB(for MySQL) |
MySQL 8.0 |
· 2.0.28.12 · 2.0.28.10 · 2.0.28.9 · 2.0.28.7 · 2.0.28.4 · 2.0.28.1 |
Application Scenarios
Finance
The finance industry has high requirements for data security and reliability with zero RPO and near-zero RTO. GaussDB(for MySQL) meets such requirements by combining the stability and reliability of commercial databases with the flexibility and cost-effectiveness of open-source databases.
Internet
The Internet industry is growing explosively. Service traffic fluctuates and peak hours are unpredictable. GaussDB(for MySQL) resources are elastically scalable, so they can adapt perfectly to the constantly fluctuating usage patterns of the industry.