Before You Start

Welcome to Distributed Cache Service (DCS). DCS is an online, distributed, in-memory cache service compatible with Redis and Memcached. It is reliable, scalable, usable out of the box, and easy to manage, meeting your requirements for high read/write performance and fast data access.

This document describes how to use application programming interfaces (APIs) to perform operations on DCS, such as creating, deleting, and scaling up DCS instances. For details about all supported operations, see API Overview.

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

Some APIs are supported only in certain regions.
DCS is continuously upgraded with new functions, and the existing APIs are inevitably adjusted. For example, new response parameters may be added.
To reduce the impact of API changes, DCS is backward compatible with APIs when possible. However, when you use DCS, you should accept and ignore unused parameters and parameter values in returned content (in JSON format).
For details about how to access DCS Redis or Memcached instances through clients in various languages, see Accessing a DCS Redis Instance and Accessing a DCS Memcached Instance.

Constraints

The number of ECSs that you can create is determined by your quota. For details, see Service Quota.
For more constraints, see API description.

Endpoints

An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. For the endpoints of all services, see Regions and Endpoints.

Concepts

Account
An account is created upon successful registration with Huawei Cloud. 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. To ensure security, create Identity and Access Management (IAM) 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).

The account name, username, and password will be required for API authentication.
Regions are defined by their geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), and Object Storage Service (OBS), are shared within the same region. AZs in the same region can communicate with each other over an intranet, but AZs in different regions cannot. You can use cloud services in locations that meet your requirements. For example, you can design applications in a location that is close to your customers or that meets specific requirements.
An AZ contains one or more physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, compute, network, storage, and other resources are logically divided into multiple clusters. AZs within a region are interconnected by high-speed optical fibers for building 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 isolating model