Before You Start

Overview

TaurusDB is an enterprise-grade cloud-native database service fully compatible with MySQL. It decouples compute from storage and uses Huawei-developed Data Function Virtualization (DFV), which scales to up to 128 TB per instance. With TaurusDB, there is no need to worry about data loss. It provides the high availability and superior performance of commercial databases at the price of open-source databases.

Data Function Virtualization (DFV) is a high-performance and high-reliability distributed storage system that is vertically integrated with databases. Storage clusters are deployed in pools to improve storage utilization.

This document describes how to use application programming interfaces (APIs) to perform operations on DB instances. For details about all supported operations, see API Overview.

API Calling

TaurusDB supports Representational State Transfer (REST) APIs, allowing you to call APIs using HTTPS. For details about API calling, see Calling APIs.

Endpoints

An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. Table 1 lists the endpoints provided by TaurusDB.

Constraints

• Currently, APIs cannot be called for single-node instances.
• For more constraints, see API description.

Concepts

• Account

  An account is created after your registration. The account has full access permissions for all of its cloud services and resources. It can be used to reset user passwords and grant user permissions. The account is a payment entity and should not be used directly to perform routine management. For security purposes, create users and grant them permissions for routine management.

• IAM User

  An IAM user is created using an account to use cloud services. Each IAM user has its own identity credentials (password and access keys).

  API authentication requires information such as the account, username, and password.

• Region

  A region is a geographic area in which cloud resources are deployed. Availability zones (AZs) in the same region can communicate with each other over an intranet, while AZs in different regions are isolated from each other. Deploying cloud resources in different regions can better suit certain user requirements or comply with local laws or regulations.

• AZ

  An AZ contains one or more 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 clusters. AZs within a region are interconnected using high-speed optical fibers to allow users to build cross-AZ high-availability systems.

• Project

  A project corresponds to a region. Projects group and isolate resources (including compute, storage, and network resources) across physical regions. Users can be granted permissions in a default project to access all resources in the region associated with the project. For more refined access control, create subprojects under a project and purchase resources in the subprojects. Users can then be assigned permissions to access only specific resources in the subprojects.

  Figure 1 Project isolation model
  
• Enterprise Project

  Enterprise projects group and manage resources across regions. Resources in enterprise projects are logically isolated from each other. An enterprise project can contain resources in multiple regions, and resources can be directly transferred between enterprise projects.

  For more information about enterprise projects and how to obtain enterprise project IDs, see Enterprise Management User Guide.