This topic describes the terms used in AnalyticDB for MySQL.

Terms

  • region

    The geographic location where the servers of AnalyticDB MySQL are located. You must specify a region when you create an AnalyticDB for MySQL V3.0 cluster. The region cannot be changed after the cluster is created.

  • zone

    A physical area within a region that has its own independent power grid and network. Zones are interconnected over the internal network. Clusters can communicate with each other at a low network latency if the clusters reside in the same zone.

  • cluster

    A group of databases. You can create multiple databases in a cluster. Databases in different clusters are isolated from each other.

  • node

    A basic unit in AnalyticDB for MySQL V3.0 clusters. A cluster consists of multiple nodes. You must specify the node specifications when you create a cluster. The node specifications include the CPU, memory, and storage capacity. For more information, see Editions.

  • elastic I/O unit (EIU)

    A unit of data that measures the storage performance of AnalyticDB for MySQL V3.0 clusters in elastic mode for Cluster Edition. You can use EIUs to separately scale out storage resources. For more information, see EIUs.

  • database

    A basic unit in AnalyticDB for MySQL V3.0. You can create one or more databases of different specifications. A database is logically composed of partitions and physically composed of nodes.

  • account

    A subject that is granted a specified set of permissions to access databases in a cluster. Account names within the same cluster must be unique.

    AnalyticDB MySQL supports the following types of accounts:
    • Alibaba Cloud account: the account that is used to create and manage clusters. For example, you can use an Alibaba Cloud account to log on to the AnalyticDB for MySQL console, change the billing method of a cluster from pay-as-you-go to subscription, scale up clusters, and delete clusters.
    • RAM user: the account that is used to create and manage clusters within the specified permissions that are granted by an Alibaba Cloud account.
    • Database account: the account that is granted a specified set of permissions to manage databases. For example, you can use a database account to create or delete databases, connect to databases, and create or delete tables.
    • Service account: the account that is used by the Alibaba Cloud technical support personnel to access your AnalyticDB for MySQL V3.0 cluster. To obtain technical support from Alibaba Cloud, you must grant permissions to the service account to authorize the Alibaba Cloud technical support personnel. When the validity period of the authorization ends, the granted permissions are automatically revoked.

    The account system and SQL syntax of AnalyticDB for MySQL V3.0 are compatible with those of MySQL. For more information, see Database accounts and permissions.

  • table

    A self-managed database consists of multiple shards. The data of a table is distributed across shards based on the hash calculation result of the distribution key specified when you create the table. When you create a table, you need only to specify a distributed key. The system assigns an appropriate number of shards for optimal performance. For more information, see CREATE TABLE.

  • partitioned table

    AnalyticDB for MySQL V3.0 supports two types of tables: fact table and dimension table. Fact tables are used to store metric values of business data. Only fact tables support partitions.

    AnalyticDB for MySQL V3.0 supports two-level partitioning. Level-1 partitioning divides a table into shards, and level-2 partitioning divides a shard into partitions. You can use a distribution key to specify shards and then use a partition key to specify partitions in a shard.

  • dimension table

    A dimension table is also known as a broadcast table. It contains descriptions of service features and has a replica on each node. Typically, dimension tables contain small volumes of data and are not frequently changed.