This topic describes the terms used in AnalyticDB for MySQL V3.0.

Terms

  • region

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

    Note You can access an AnalyticDB for MySQL V3.0 cluster only by using Alibaba Cloud Virtual Private Cloud (VPC). When you purchase an AnalyticDB for MySQL V3.0 cluster, you must also purchase an Elastic Compute Service (ECS) instance within the same region to access the cluster.
  • zone

    A zone is 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

    Databases belong to clusters. You can create multiple databases in a cluster. Databases in different clusters are isolated from each other.

  • node

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

  • EIU

    An elastic I/O unit (EIU) is the unit of data that measures the storage performance of AnalyticDB for MySQL V3.0. You can use EIUs to separately scale out storage resources. For more information, see EIUs.

  • database

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

  • account

    Accounts are subjects that are granted a specified set of permissions used to access databases in clusters. Account names within the same cluster must be unique.

    AnalyticDB for MySQL V3.0 supports the following types of accounts:
    • Alibaba Cloud account: the account 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 out clusters, and delete clusters.
    • Resource Access Management (RAM) user: the account used to create and manage clusters within the specified permissions that are granted by an Alibaba Cloud account.
    • Database account: an account that is granted a specified set of permissions used 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 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 in shards based on the hash calculation result of the distribution key specified by Distributed Key when you create the table. When you create a table, you need only to specify 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. Only fact tables support partitions.

    AnalyticDB for MySQL V3.0 supports two levels of partitions. Level-1 partitions are divided into shards. Level-2 partitions are specified within shards. You can use distribution keys to specify multiple shards and use partition keys to specify level-2 partitions from a specific dimension.