Single-Node Redis

Features

1. Low-cost and suitable for development and testing

   Single-node instances are 40% cheaper than master/standby DCS instances, suitable for setting up development or testing environments.

2. Data not persisted

   Data persistence is not ensured through one master node for single-node instances. The data cannot be backed up.

Architecture

Figure 1 shows the architecture of a single-node DCS Redis instance.

• For Redis 4.0 and later, you can specify a port or use the default port 6379. In the following architecture, port 6379 is used. If you have customized a port, replace 6379 with the actual port.
• You cannot upgrade the Redis version for an instance. For example, a single-node DCS Redis 4.0 instance cannot be upgraded to a single-node DCS Redis 5.0 instance. If your service requires the features of higher Redis versions, create a DCS Redis instance of a higher version and then migrate data from the old instance to the new one.

Figure 1 Single-node DCS Redis instance architecture

Architecture description:

• VPC

  The VPC where all nodes of the instance run.

• Application

  The client of the instance, which is the application running on an Elastic Cloud Server (ECS).

  DCS Redis instances are compatible with Redis, and can be accessed through open-source clients. For examples of accessing DCS instances with different programming languages, see instance access instructions.

• DCS instance

  A single-node DCS instance, which has only one node and runs one Redis process.