This topic describes the terms of ApsaraDB for Redis.

Term Description
ApsaraDB for Redis A high-performance, key-value storage database service that supports caching and storage. ApsaraDB for Redis is developed based on BSD open source protocol.
instance ID The ID of an instance. Each instance corresponds to a user space and serves as the basic unit of the ApsaraDB for Redis service. Different ApsaraDB for Redis instance specifications have different limits on instance capacities, such as the number of connections, bandwidth, and CPU capability. You can view the list of your instance IDs in the ApsaraDB for Redis console.
standard master-replica instance An ApsaraDB for Redis instance that is built on top of a master-replica architecture. Master-replica instances provide limited capacity and performance. However, you can change the architecture of a master-replica instance to an instance of another architecture, such as a cluster instance or a read/write splitting instance.
cluster instance An ApsaraDB for Redis instance that runs in a cluster architecture with scalability. Cluster instances provide higher scalability and performance. However, the instances provide limited features.
endpoint The host address that is used to connect to ApsaraDB for Redis. The endpoint is displayed as a domain name. To obtain the endpoint, log on to the ApsaraDB for Redis console and choose Instance Information > Connection Information.
connection password The password used to connect to an ApsaraDB for Redis instance. The password is in the Instance ID:Custom password format. For example, if you set the password to 1234 when you purchase an instance and the instance ID is xxxx, the connection password is xxxx:1234.
eviction policy The eviction policy that is the same as that of the open source Redis. For more information, see Using Redis as an LRU cache.
database The databases that can be created in an ApsaraDB for Redis instance. Each ApsaraDB for Redis instance can contain up to 256 databases: DB 0 to DB 255. By default, data is written into DB 0.