vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/gaussdb_mysql/umn/gaussdb_01_0001.html
Wang , Deng Ke e944469104 gaussdb UMN 20221230 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com>
Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
2023-08-13 18:46:36 +00:00

2.1 KiB
Raw Permalink Blame History

Basic Concepts

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

  • Cluster: GaussDB(for MySQL) uses the cluster architecture, with one primary node and multiple read replicas.
  • 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, fire extinguishing, moisture-proof, and 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 cost-effective and low-latency network connections that are unaffected by faults that may occur in other AZs. As a result, provisioning GaussDB(for MySQL) DB 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 class: resource configuration of each node, for example, 16 vCPUs and 64 GB.
Parent topic: Introduction