TencentDB for Redis

TencentDB for Redis
Product Introduction
Product Documentation©2013-2022 Tencent Cloud. All rights reserved.

Page 1 of 52

TencentDB for Redis

Copyright Notice©2013-2024 Tencent Cloud. All rights reserved.
Copyright in this document is exclusively owned by Tencent Cloud. You must not reproduce, modify, copy or distributein any way, in whole or in part, the contents of this document without Tencent Cloud's the prior written consent.
Trademark Notice

All trademarks associated with Tencent Cloud and its services are owned by Tencent Cloud Computing (Beijing)
Company Limited and its affiliated companies. Trademarks of third parties referred to in this document are owned bytheir respective proprietors.
Service Statement
This document is intended to provide users with general information about Tencent Cloud's products and services
only and does not form part of Tencent Cloud's terms and conditions. Tencent Cloud's products or services are
subject to change. Specific products and services and the standards applicable to them are exclusively provided for in
Tencent Cloud's applicable terms and conditions.

©2013-2022 Tencent Cloud. All rights reserved.

Page 2 of 52

TencentDB for Redis

Contents
Product Introduction
Overview
Features
Strengths
Use Cases
Storage Engine
Product Series
Memory Edition (Standard Architecture)
Memory Edition (Cluster Architecture)
CKV Edition (Standard Architecture)
CKV Edition (Cluster Architecture)
Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Relevant Concepts
Relevant Products©2013-2022 Tencent Cloud. All rights reserved.

Page 3 of 52

TencentDB for Redis

Product Introduction
Overview：

Last updated 2023-05-23 10:59:20
TencentDB for Redis is a cache database provided by Tencent Cloud based on the Redis protocol that features highavailability, reliability, and flexibility. Compatible with Redis 2.8, 4.0, 5.0, and 6.2 protocols and available in bothstandard and cluster architectures, it supports up to 8 TB of storage capacity and tens of millions of concurrent
requests, meeting the needs of different scenarios such as caching, storage, and computing.

Relevant Concepts
TencentDB for Redis generally involves the following concepts:
Instance: A database environment running independently in Tencent Cloud. One database instance can containmultiple user-created databases.
VPC: A custom virtual network space that is logically isolated from other resources.
Security group: Security access control to TencentDB for Redis instances by specifying IP, protocol, and port rules
for instance access.
Regions and AZs: Physical location of a TencentDB for Redis instance and other resources.
Tencent Cloud console: Web-based UIs.
Read/write separation: TencentDB for Redis supports switching read/write separation on or off. It targets atbusiness scenarios with more reads and less writes, which can well cope with read requests concentrating on hotspot
data. It supports up to 1-master 5-replica mode to offer 5x read performance scalability.

Relevant Products
TencentDB for Redis generally involves the following products:
You can deploy your computing services by purchasing Cloud Virtual Machine (CVM) instances. For more
information, see CVM.
You can use Tencent Cloud Observability Platform (TCOP) to monitor the running status of your TencentDB for Redis
instances. For more information, see TCOP.
You can write code to call TencentCloud APIs to access Tencent Cloud products and services. For more information,
see the TencentCloud API documentation.

©2013-2022 Tencent Cloud. All rights reserved.

Page 4 of 52

TencentDB for Redis

Features：

Last updated 2023-05-23 11:06:22

Product Features
Ease of use
Open-source compatibility: TencentDB for Redis is fully compatible with the open-source Redis protocol, so you
can directly use Redis clients to communicate with TencentDB for Redis instances without any code modifications.
Installation-free use: You can directly purchase TencentDB for Redis instances on the purchase page and selectthe desired system architecture, with no need to install them on your own.
Cloud migration: TencentDB for Redis supports cold and hot data migration in various self-built databaseenvironments such as self-built Tencent Cloud-based, VPN-based, Direct Connect-based, and IDC-based
environments.

Rich specifications
TencentDB for Redis offers a choice of 0.25 GB–8 TB capacity specifications available in Standard and Cluster
Editions.
Memory Edition (Standard Architecture) supports 1–5 replicas to meet the different requirements for availability andperformance of your business in different scenarios. If the number of replicas is greater than or equal to 1, read/write
separation can be enabled to extend the read performance through replica nodes.
TencentDB for Redis Memory Edition (Cluster Architecture) supports horizontal scaling of 1–128 shards and replica
scaling of 1–5 replica, where the scaling and specification adjustment are virtually imperceptible to the business,
maximizing the system availability.

Ultra-High PerformanceHigh throughput: The Standard Edition has a performance of up to 100,000+ QPS for concurrent response, and theCluster Edition supports up to tens of millions of QPS as the number of shards increases. Their ultra-high performancecan perfectly meet the needs in most business scenarios ranging from gaming, mobile apps to advertising andecommerce.
Low latency: TencentDB for Redis delivers stable low-latency response, where 99% requests can be responded towithin 1 ms or 10 ms under 50% or 90% load respectively.
Read expansion: In hot key scenarios, TencentDB for Redis allows dynamically increasing replicas to expand theread performance. It supports up to 5 replicas to read up to 500,000 hot keys.
Write expansion: The performance of the Cluster Edition equals to the shard quantity multiplied by the performance
per shard and increases linearly as the shard quantity increases between 3 and 128.

©2013-2022 Tencent Cloud. All rights reserved.

Page 5 of 52

TencentDB for Redis

Flexible architecture
TencentDB for Redis supports multiple system architectures to meet the needs in different business scenarios. You
can deploy the most appropriate architecture based on your business needs.
Standard architecture: It refers to the edition that supports one or more replicas (nodes other than the master node)and is the most common Redis edition.
Cluster architecture: It is a new edition of Redis built by Tencent Cloud based on Community Edition of Redis
Cluster. It uses a distributed architecture to enable elastic scaling and features high flexibility, availability, andperformance of tens of millions of QPS.
Architecture upgrade: TencentDB for Redis allows you to upgrade from standard architecture to cluster architecture
if the performance and capacity of standard architecture are insufficient.
Read/Write separation: Automatic read/write separation is implemented at the proxy layer. The proxy writes data
only to the master node, while read requests are automatically routed to the configured read-only nodes by loadbalancing.
Multi-AZ deployment: It refers to the disaster recovery architecture where the master and replica nodes of an
instance are deployed in different AZs in the same region to deliver a higher availability.
Global replication: Based on the original master-replica replication scheme, a new log file is added for remote
replication to ensure the eventual data consistency for instances in different regions in the replication group. Thissolves the problem of cross-region data inconsistency and offers region-level disaster recovery capabilities.
Automatic failover: TencentDB for Redis adopts a master/replica hot backup architecture. In case of failure of themaster, the access can be switched to the replica in a matter of seconds. The switch process does not require any
operations at your side, reducing the labor and time costs of developing a master/replica system architecture.

Data Security
RDB persistence: The TencentDB backend service periodically creates snapshots for the data stored in the storageengine according to the backup policy to generate RDB files and then saves them in disks for data persistence.
Network security protection: TencentDB for Redis supports configuring security groups in VPCs to implement
allowlist-enabled network access control, which ensures the security and reliability of network environments.
Account authentication: TencentDB for Redis allows you to authorize root accounts, sub-accounts, or acrossaccounts, so you can manage your resources at a fine-grained level and benefit from enterprise-grade security
protection.
Data isolation: TencentDB for MongoDB supports multiple layers of data isolation between different regions, AZs,
networks, and account levels to ensure the data security and integrity.

Smart Ops
System monitoring: TencentDB for Redis is completely imperceptible to businesses. You can configure alarm rules
in TCOP, which provides more than 30 automated monitoring metrics. This helps you stay up to date with the runningstatus of your instances and quickly troubleshoot problems.

©2013-2022 Tencent Cloud. All rights reserved.

Page 6 of 52

TencentDB for Redis**TencentDB for DBbrain (DBbrain)**: It monitors and diagnoses database instance exceptions in real time (including
slow logs, big keys, hot keys, and delays), automatically generates health reports, and gives expert optimizationsuggestions. This helps you promptly optimize the database performance.
Management APIs: TencentDB for Redis offers a complete set of management APIs to implement diverse selfservice resource management and Ops features.

Comparison with Self-Built Databases
TencentDB for Redis provides the capabilities of NoSQL databases as a service, which has great strengths in termsof flexibility, ease of use, high availability, fully managed Ops, data security, and data reliability.

Item

Self-Built Redis

TencentDB for Redis

Performance

80,000–10,000/shard

80,000–10,000/shard

For a self-built database, storage
servers are costly. If you want aWith TencentDB, you don't have to invest in
hardware and software. You have a variety ofhigh-availability master/replica
instance, you will have to purchasespecification options to choose from. You canapply for necessary resources based on yourthree servers, which may cause

actual business conditions to maximize theresource redundancy and waste. In
addition, you need to recruit

resource utilization. In addition, you can use thefree-of-charge features such as management,

professional databaseadministrators, which also means

backup, clone, monitoring, and alarm. In
conclusion, TencentDB has a higher costhigh labor costs.

effectiveness with similar resource costs.

> 60s

< 60s

Cost

HA

Hot backup is supported based on two or moreservers, with automatic disaster recovery, failover,Availability

You need to fix failures and build
master/replica cluster architecture

and imperceptible migration features available,delivering a 99.95% availability.

on your own.

Read preference from replica databases is
supported to ensure high concurrent readcapability.

Scaling

Business scaling is much slower
because you must do the tedious

Scaling can be performed quickly as needed, withno momentary disconnections, downtime, or read-tasks on your own, like procuring
hardware, hosting data centers,

only access.

and redeploying applications. In
addition, double write and data
migration cause momentary©2013-2022 Tencent Cloud. All rights reserved.

Page 7 of 52

TencentDB for Redis

disconnections during switch andinvolve high data risks.
Automatic read/write separation is supported andRead/write
separation

Separate development is required.

can be enabled/disabled based on the businessneeds.

Isolation

CPU and memory isolation

CPU, memory, traffic, and connection isolation

Multi-accountNot supported

Supported

Blocklist

Not supported

High-risk commands can be disabled.
More than 30 metrics for clusters and nodes are

Monitoring

Only a few monitoring metrics areavailable, including unique ones for latency, traffic,

available, which are collected by
the server.

big key, and hot key. Alarms can be triggered forthem, so you can perform Ops tasks proactively toprevent risks.

©2013-2022 Tencent Cloud. All rights reserved.

Page 8 of 52

TencentDB for Redis

Strengths：

Last updated 2022-01-04 11:23:55

Wide Variety of Product Specifications
TencentDB for Redis offers a choice of 0.25 GB–8 TB capacity specifications available in Standard and Cluster
Editions.

Elastic Scaling
An instance can be scaled quickly in the console without having to stop the services. No operations are required atyour side.

Ultra-high Performance
The Standard Edition has a performance of up to 100,000+ QPS, and the Cluster Edition supports tens of millions of
QPS. Their ultra-high performance can perfectly meet the needs in most business scenarios ranging from gaming,
mobile apps to advertising and ecommerce.

Rich Monitoring Capabilities
TencentDB for Redis boasts a rich set of metrics and alarms that are monitored and visually displayed for clear
insights into the data, helping you identify risks before they appear and troubleshoot problems quickly.

Convenient DTS Service
TencentDB for Redis supports cold and hot data migration in various self-created database environments such as
self-created Tencent Cloud-based, VPN-based, Direct Connect-based, and IDC-based environments.

Automatic Disaster Recovery
TencentDB for Redis adopts a primary/replica hot backup architecture. In case of failure of the primary server, theaccess can be switched to the replica in a matter of seconds. The switch process does not require any operations atyour side, reducing the labor and time costs of developing a primary/replica system architecture.

©2013-2022 Tencent Cloud. All rights reserved.

Page 9 of 52

TencentDB for Redis

Use Cases：

Last updated 2022-04-28 15:45:13

GamingIn the gaming industry, non-role data such as leaderboard data can be stored in TencentDB for Redis for quick
access, and the native Sorted Set data type of Redis can readily help you sort player data.

Internet and App
In internet and app businesses, basic user data can be cached into TencentDB for Redis to improve the read/write
performance. Further, static images and resources can be cached there too to speed up app loading.

©2013-2022 Tencent Cloud. All rights reserved.

Page 10 of 52

TencentDB for Redis

Ecommerce Display
In ecommerce display, data such as product images and recommendations can be stored in TencentDB for Redis forquick access. In addition, the high QPS performance (up to tens of millions) of Redis can sustain high concurrent
requests, making it ideal for large-scale campaigns (e.g., flash sales).

©2013-2022 Tencent Cloud. All rights reserved.

Page 11 of 52

TencentDB for Redis©2013-2022 Tencent Cloud. All rights reserved.

Page 12 of 52

TencentDB for Redis

Storage Engine：

Last updated 2022-01-04 11:30:00

Memory Edition Engine
The Memory Edition engine provides a native Redis experience and supports a myriad of scenarios. It supports both
Redis standard and cluster deployment architectures to meet the requirements of different business scenarios.
Editions supported by the Memory Edition engine include:
Memory Edition (standard architecture): when the number of replicas is greater than 0, data is synced between themaster node and the replica nodes (slaves) in real time. When the master node fails, automatic failover will be
performed in a matter of seconds, and a replica node will take over the business in an imperceptible manner. The
master/slave architecture guarantees high availability of system services and provides 0.25–64 GB of storage
capacity.
Memory Edition (cluster architecture): a cluster instance uses a distributed architecture, which allows flexible selectionof shard quantity, shard capacity, and replica quantity and enables scaling imperceptible to the business. It provides 2
GB–8 TB of storage capacity and a performance of tens of millions of QPS.

©2013-2022 Tencent Cloud. All rights reserved.

Page 13 of 52

TencentDB for Redis

Product Series
Memory Edition (Standard Architecture)：

Last updated 2023-05-23 10:25:15
TencentDB for Redis Memory Edition (Standard Architecture) refers to the edition that supports one or more replicas(a replica refers to a non-master node), which is the most common Redis edition. It is compatible with protocols andcommands of Redis 2.8, 4.0, 5.0, and 6.2 and features data persistence and backup, making it suitable for scenarios
where high data reliability and availability are required. A master node provides daily service access, while a replica
node ensures high availability (HA). In case that the master node fails, the system will automatically switch to thereplica node to guarantee business continuity.
Taking 1 replica as an example, Memory Edition (Standard Architecture) is as follows:

Replica Description©2013-2022 Tencent Cloud. All rights reserved.

Page 14 of 52

TencentDB for Redis

Memory Edition (Standard Architecture) supports 1–5 replicas to meet the different requirements for availability andperformance of your business in different scenarios. All replicas of Memory Edition (Standard Architecture) play a rolein supporting system's high availability, so the more replicas, the higher the availability. If the number of replicas isgreater than or equal to 1, read/write separation can be enabled to extend the read performance through replica
nodes.
Definition:
Master node: A Redis node that provides read and write capabilities.
Replica node: A Redis node that provides high availability or read-only capability. A master node cannot be a replica
node.
Replica support:
Instance Version

Supported Replica Number

Read/Write Separation

Redis 2.8 Memory Edition (Standard
Architecture)1

Not supported

Redis 4.0 Memory Edition (Standard
Architecture)

1-5

Supported

1-5

Yes

1-5

Supported

Redis 5.0 Memory Edition (Standard
Architecture)
Redis 6.2 Memory Edition (Standard
Architecture)**Read-only replica (read/write separation)**:Supported editions: TencentDB for Redis 4.0 Memory Edition (Standard Architecture) and above instance. When thenumber of replicas is greater than 1, automatic read/write separation can be enabled to extend the read performancevertically. Up to 5 replica nodes can be supported.
How it works: After read-only replica is enabled, write requests will be routed to the master node, while read requests
will be routed to all replica nodes through the load balancing algorithm and no longer be processed by the masternode. This read/write separation feature is provided by the Proxy component built in TencentDB for Redis.
Enabling/Disabling: You can enable or disable read-only replica on the instance creation page in the TencentDB for
Redis Console or through TencentCloud API.

FeaturesService reliability (1-5 replicas)
With a dual-server master/slave architecture, the master and slave nodes reside on different physical machines with

©2013-2022 Tencent Cloud. All rights reserved.

Page 15 of 52

TencentDB for Redisthe master node providing external access. You can perform data CRUD using the Redis command line or client. In
case that the master node fails, the proprietary HA system will automatically perform master/slave switchover toensure smooth operation of the business.
Data reliability (1-5 replicas)
The data persistence feature is enabled by default. Memory Edition (Standard Architecture) supports data backup.
You can roll back or clone instances for backup files to effectively cope with data maloperations and other issues.

Use Limits
Memory Edition (Standard Architecture) supports 0.25–64 GB of storage capacity. For higher specifications, use
Cluster Edition that supports up to 8 TB of capacity.
Memory Edition (Standard Architecture) supports up to 100,000 QPS (SET command concurrencies). If you need ahigher QPS, you can choose multi-replica read/write separation or use Redis Cluster Edition that supports tens of
millions of QPS.

Command Compatibility
For more information on the supported commands, see Command Compatibility Overview.

©2013-2022 Tencent Cloud. All rights reserved.

Page 16 of 52

TencentDB for Redis

Memory Edition (Cluster Architecture)：

Last updated 2023-03-14 15:36:05
TencentDB for Redis Memory Edition (Cluster Architecture) is a new edition of Redis built by Tencent Cloud based on
Community Edition of Redis Cluster, which is compatible with Redis 4.0, 5.0, and 6.2 commands. It uses a distributed
architecture to enable elastic scaling and features high flexibility, availability, and performance of tens of millions of
QPS. Specifically, it supports horizontal scaling of 1–128 shards and replica scaling of 1–5 replica sets, where thescaling and migration are virtually imperceptible to the business, maximizing the system availability.

Use cases
Master/replica high-availability (HA) scenarios
Memory Edition (Cluster Architecture) allows you to configure a replica set for a single node to achieve highmaster/replica availability. It features dual-server hot backup and automatic failover to ensure high reliability and©2013-2022 Tencent Cloud. All rights reserved.

Page 17 of 52

TencentDB for Redis

availability of the Redis service.
Read/write separation scenarios
When the number of replica nodes is greater than or equal to 1, automatic read/write separation can be enabled for
the TencentDB for Redis instance to extend the read performance of a single node. Up to five replica sets can besupported, and read access weights across the master and replica nodes can be configured.
Multi-shard high-performance scenarios
Memory Edition (Cluster Architecture) automatically enables automatic sharding and achieves horizontal scaling ofsystem performance by assigning different keys to multiple nodes.

Cluster specifications
Shard specification (GB): 1, 2, 4, 8, 12, 16, 20, 24, 32, 40, 48, 64.
Shard quantity: 1, 3, 5, 8, 12, 16, 24, 32, 40, 48, 64, 80, 96, 128.
Replica quantity: 1, 2, 3, 4, 5.

Cluster mode
In cluster mode, data is automatically sharded. The system provides data load balancing and migration capabilities.
The cluster mode is compatible with certain commands of the non-cluster mode, mainly reflected in cross-slot data
access. For more information, see Command compatibility.

Replica description
When there is only one replica, Redis provides master/replica real-time hot backup for high data reliability andavailability (server-level HA is supported in a single AZ). When the HA system detects a node failure, it requests forswitching to a replica node and adds a new replica node to the system.
When the number of replicas is greater than 1, Redis provides master/replica real-time hot backup with the replica
nodes being read-only.

Features
Flexibility
Memory Edition (Cluster Architecture) supports horizontal scaling of 1–128 nodes and scaling of 1-5 replica sets,making it ideal for various scenarios through instance specification adjustment.
Availability©2013-2022 Tencent Cloud. All rights reserved.

Page 18 of 52

TencentDB for Redis

In Memory Edition (Cluster Architecture), scaling of shard quantity and replica quantity are virtually imperceptible tothe business, maximizing the system availability.
Compatibility
Memory Edition (Cluster Architecture) supports use cases of the Community Edition of Redis Cluster and Codis and iscompatible with clients such as Jedis.
Ops
Memory Edition (Cluster Architecture) maximizes system capability and has advanced features such as shard-levelmonitoring and management, data migration and load balancing, as well as monitoring of big and hot keys, whichfacilitate smart monitoring and Ops of the cluster service.

Command compatibility
For more information on the supported commands, see Command Compatibility Overview.

©2013-2022 Tencent Cloud. All rights reserved.

Page 19 of 52

TencentDB for RedisCKV Edition (Standard Architecture)：

Last updated 2021-07-07 16:18:02
Note:
TencentDB for Redis CKV Edition is currently unavailable. We recommend TencentDB for Redis Memory Edition foryou.
TencentDB for Redis CKV Edition (standard architecture) uses a master/replica node deployment architecture toprovide data persistence and backup, making it suitable for scenarios that require both high data reliability andavailability.
A master node provides daily service access, while a replica node ensures high availability (HA). In case that themaster node fails, the system will automatically switch to the replica node to guarantee business continuity. CKVEdition (standard architecture) is compatible with Redis 3.2 commands and protocols and supports a specification of
4–384 GB to meet the needs of large-capacity storage.

Features
Robust service
With a dual-server master/replica architecture, the master and replica nodes reside on different physical machineswith the master node providing external access and the replica node providing data backup and HA. You can perform©2013-2022 Tencent Cloud. All rights reserved.

Page 20 of 52

TencentDB for Redis

data CRUD using the Redis command line or client. In case that the master node fails, the proprietary HA system willautomatically perform master/replica switchover to ensure smooth operation of the business.-Reliable data
The data persistence feature is enabled by default with all data stored in disks. CKV Edition (standard architecture)
supports data backup. You can roll back or clone instances from backup sets to effectively cope with data
misoperations and other issues.
Lower latency
CKV uses a high-performance network platform and a proxy-free architecture, which significantly reduce the accesslatency and network latency by up to 60% in high-load scenarios.
Read-only replicas
CKV Edition (standard architecture) can greatly improve the read performance by 40% on average by enabling readonly replica. The read-only replica feature is not enabled by default. Currently, you can submit a ticket for application.
Due to the replication delay between the CKV master node and replica node, after the read-only replica feature isenabled, some legacy data may be read; therefore, please confirm whether your business can accept slight data
inconsistency before enabling this feature.
Smooth upgrade
With unique schemes, CKV Edition (standard architecture) can ensure the business-imperceptible version upgrade,thus maximizing the service availability.

Use Limits
CKV Edition (standard architecture) supports up to 120,000 QPS. If you need a higher QPS, you can choose thecluster architecture that supports tens of millions of QPS.
-The minimum unit of pttl in CKV Edition is second, which is different from Redis Community Edition.
Currently, string-type keys are supported, and a value can be up to 32 MB.
The instance connection method is instance ID:password , which is different from that of the Memory Editionin standard or cluster architecture.
The time complexity implemented by the dbsize command is O(n). When the command is executed, it needs totraverse all keys in the current database; therefore, it should be used with caution.
There is a built-in string-type key: {ckv_plus_pub_sub}_patterns , which is used to support the pub/sub
feature. If you need to use this feature, please do not delete this key; otherwise, subscriptions will become invalid.
Event notification currently does not support notifications of expiration and eviction policy.
The eviction policy currently only supports volatile-lru . The eviction mechanism can be disabled with thecorresponding parameter maxmemory-policy .

Connection Example©2013-2022 Tencent Cloud. All rights reserved.

Page 21 of 52

TencentDB for RedisCKV Edition (standard architecture) only supports the password format: instance id:password . For example,
if your instance ID is crs-bkuza6i3 and the password is abcd1234, the connection command is redis-cli -h IP
address -p port -a crs-bkuza6i3:abcd1234 .

Compatibility
Commands supported by CKV Edition (standard architecture):connectionGroup

geo Group

hashesGroup

hyperloglog
Group

keys
Group

lists
Group

pub/sub
Group

auth

geoadd

hdel

pfadd

del

lindexpsubscribechogeohashhexists

pfcount

scan

linsertpubsubping

geoposhgetpfmergeexistsllenpublishquit

geodisthgetall-

expirelpop

punsubsc

selectgeoradius

hincrby-expireat

lpush

subscribe-

georadiusbymember

hincrbyfloat

-

keys

lpushxunsubscr

-

-

hkeys

-

type

lrange

-

-

-

hlen

-

move

lrem

-

-

-

hmget

-

ttl

lset

-

-

-

hmset

-

persist

ltrim

-

-

-

hset

-

pexpire

rpop

-

-

-

hsetnx-pexpireatrpoplpush---hstrlen

-

pttl

rpush

-

-

-

hvals

-

randomkey

rpushx

-

-

-

hscan

-

rename

-

-

-

-

-

-

renamenx

-

-

-

-

-

-

sort

-

-

sets Group

sorted sets Group©2013-2022 Tencent Cloud. All rights reserved.

strings Grouptransactions Group

scripting Group

Page 22 of 52

TencentDB for Redis

sadd

zadd

appenddiscard

eval

scard

zcard

bitcount

exec

script debug

sdiff

zcount

bitop

multi

script exists

sdiffstore

zincrbybitposunwatchscript flush

sinterzinterstore

decr

watch

script killsinterstore

zlexcountdecrby-script load

sismemberzrangeget--smembers

zrangebylex

getbit

-

-

smove

zrangebyscoregetrange

-

-

spop

zrank

getset--srandmember

zrem

incr

-

-

srem

zremrangebylex

incrby

-

-

sscan

zremrangebyrank

incrbyfloat--

sunionzremrangebyscore

mget

-

-

sunionstore

zrevrange

mset

-

-

-

zrevrangebylex

msetnx---zrevrangebyscorepsetex---zrevrank

set

-

-

-

zscan

setbit---zscore

setex

-

-

-

zunionstore

setnx

-

-

-

-

setrange

-

-

-

-

strlen--Commands not supported by CKV Edition (standard architecture):cluster Group

connection

keys©2013-2022 Tencent Cloud. All rights reserved.

lists

scriptingserverstrings

Page 23 of 52

TencentDB for Redis

Group

Group

Group

Group

Group

Group

cluster addslots

swapdb

touch

blpop

evalshabgrewriteaof

bitfieldcluster countfailure-reports-

restorebrpop-

bgsave-clustercountkeyinslot-

objectbrpoplpush-

client kill-cluster delslots-

unlink--client list-

cluster failover

-

wait

-

-

clientgetname-cluster forget-migrate--client pause

-

-

dump

-

-

client reply-

cluster info

-

-

-

-

clientsetname-cluster keyslot

-

-

-

-

commandcount-cluster meet

-

-

-

-

commandgetkeys-cluster nodes

-

-

-

-

commandinfo-

cluster replicate

-

-

-

-

config get-cluster reset

-

-

-

-

configrewrite-clustersaveconfig

-

-

-

-

config set-

cluster setconfig-epoch

-

-

-

-

configresetstat-cluster setslot

-

-

-

-

debug
object-cluster slaves

-

-

-

-

debug
segfault-clustergetkeysinslot©2013-2022 Tencent Cloud. All rights reserved.

Page 24 of 52

TencentDB for Rediscluster slots

-

-

-

-

flushall-readonly

-

-

-

-

flushdb-

readwrite

-

-

-

-

lastsave

-

-

-

-

-

-

monitor

-

-

-

-

-

-

role

-

-

-

-

-

-

save

-

-

-

-

-

-

shutdown

-

-

-

-

-

-

slaveof

-

-

-

-

-

-

slowlog

-

-

-

-

-

-

sync

-

©2013-2022 Tencent Cloud. All rights reserved.

Page 25 of 52

TencentDB for RedisCKV Edition (Cluster Architecture)：

Last updated 2021-09-26 15:40:32
Note:
TencentDB for Redis CKV Edition is currently unavailable. We recommend TencentDB for Redis Memory Edition foryou.
TencentDB for Redis CKV Edition (cluster architecture) provides dual-replica cluster instances, which break thesingle-thread bottleneck to meet your business needs for large capacity or high performance. CKV Edition (clusterarchitecture) is compatible with Redis 3.2 protocols and commands and supports up to 128 shards of 12 GB–48 TB
capacity.

Features
Robust service
With a dual-server master/replica architecture, the master and replica nodes reside on different physical machineswith the master node providing external access and the replica node providing data backup and high availability (HA).
You can perform data CRUD using the Redis command line or client. In case that the master node fails, theproprietary HA system will automatically perform master/replica switchover to ensure smooth operation of thebusiness.
Reliable data
The data persistence feature is enabled by default with all data stored in disks. CKV Edition (cluster architecture)
supports data backup. You can roll back or clone instances from backup sets to effectively cope with data
misoperations and other issues.
-Lower latency
CKV uses a high-performance network platform and a proxy-free architecture, which significantly reduce the accesslatency and network latency by up to 60% in high-load scenarios.
Read-only replica
CKV Edition (cluster architecture) can greatly improve the read performance by 40% on average by enabling readonly replica. The read-only replica feature is not enabled by default. Currently, you can submit a ticket for application.
Due to the replication delay between the CKV master node and replica node, after the read-only replica feature isenabled, some legacy data may be read; therefore, please confirm whether your business can accept slight data
inconsistency before enabling this feature.
Smooth upgrade
With unique schemes, CKV Edition (cluster architecture) can ensure the business-imperceptible version upgrade, thus
maximizing the service availability.

©2013-2022 Tencent Cloud. All rights reserved.

Page 26 of 52

TencentDB for Redis

Use Cases
Large volume of data in a single instanceCKV Edition (cluster architecture) uses a distributed architecture, making it suitable for storing high volumes of data in
one single instance. Its capacity can exceed the upper limit of 384 GB of CKV Edition (standard architecture).
High QPS and concurrence requirements
CKV Edition (cluster architecture) uses a distributed architecture where reads and writes are spread across multiple
nodes. Under the condition that the keys are evenly distributed, its QPS can increase linearly with the number ofnodes. At present, it supports a maximum of 128 shards and 10 million QPS.
Insensitive protocol support
CKV Edition (cluster architecture) supports slightly less protocols than the open-source editions.

Connection Example
CKV Edition (cluster architecture) only supports the password format: instance id:password . For example, if
your instance ID is crs-bkuza6i3 and the password is abcd1234, the connection command is redis-cli -h IP address -p
port -a crs-bkuza6i3:abcd1234.

Use Limits
The minimum unit of pttl in CKV Edition is second, which is different from Redis Community Edition.
Currently, string-type keys are supported, and a value can be up to 32 MB, which are different from Redis Community
Edition.
Except MSET and MGET, other batch operations require that all the keys be in the same slot, otherwise an error
message "CROSSSLOT Keys in request don't hash to the same slot" may occur.
When a shard is full, subscribe / psubscribe takes up a certain amount of memory, which affects the additionof a new subscription, but does not affect the publish of the subscribed channel.

Notes
At present, the size of a single shard in CKV Edition (cluster architecture) is 4 GB by default; therefore, it isrecommended that the value of a single key not exceed 4 GB.
CKV Edition (cluster architecture) currently provides monitoring at the cluster dimension.

©2013-2022 Tencent Cloud. All rights reserved.

Page 27 of 52

TencentDB for Redis

Compatibility
Commands supported by CKV Edition (cluster architecture):connectionGroup

geo Group

hashesGroup

hyperloglog
Group

keys
Group

lists
Group

pub/sub
Group

auth

geoadd

hdel

pfadd

del

lindexpsubscribeechogeohashhexists

pfcount

existslinsertpubsubping

geoposhgetpfmerge

expirellenpublish tim

quit

geodisthgetall-

expireatlpop

punsubscr

selectgeoradius

hincrby

-

type

lpush

subscribe-

georadiusbymember

hincrbyfloat-

ttl

lpushxunsubscrib

-

-

hkeys

-

persistlrange

-

-

-

hlen

-

pexpire

lrem

-

-

-

hmget

-

pexpireat

lset

-

-

-

hmset

-

pttl

ltrim

-

-

-

hset

-

rename

rpop

-

-

-

hsetnx-renamenx

rpoplpush---hstrlen

-

sort

rpush

-

-

-

hvals

-

-

rpushx

-

-

-

hscan

-

-

-

-

sets Group

sorted sets Groupstrings Grouptransactions Group

server Group

sadd

zadd

appenddiscardcommand

scard

zcard

bitcount

exec

dbsizesdiff

zcount

bitop

multi

-

sdiffstore

zincrbybitposunwatch-sinterzinterstore

decr

watch

-

©2013-2022 Tencent Cloud. All rights reserved.

Page 28 of 52

TencentDB for Redissinterstore

zlexcountdecrby--sismemberzrangeget--smembers

zrangebylex

getbit

-

-

smove

zrangebyscoregetrange

-

-

spop

zrank

getset--srandmember

zrem

incr

-

-

srem

zremrangebylex

incrby

-

-

sscan

zremrangebyrank

incrbyfloat--

sunionzremrangebyscore

mget

-

-

sunionstore

zrevrange

mset

-

-

-

zrevrangebylex

msetnx---zrevrangebyscorepsetex---zrevrank

set

-

-

-

zscan

setbit---zscore

setex

-

-

-

zunionstore

setnx

-

-

-

-

setrange

-

-

-

-

strlen--Commands not supported by CKV Edition (cluster architecture):cluster Group

connection
Group

keys
Group

lists
Group

scriptingGroup

serverGroup

stringsGroup

cluster
addslots

swapdb

touch

blpop

eval

bgrewriteaof

bitfield-

restorebrpop

evalshabgsave--objectbrpoplpush

scriptclient kill-cluster countfailure-reports
cluster delslots©2013-2022 Tencent Cloud. All rights reserved.

Page 29 of 52

TencentDB for Redis

debug
cluster failover-

unlink-scriptexistsclient list-

cluster forget

-

wait

-

script flush

clientgetname-cluster meet-

migrate-script killclient pause-

cluster
replicate

-

dump

-

script load

client reply-

cluster reset

-

scan

-

-

clustersaveconfig

-

keys

-

-

commandcount-cluster setconfig-epoch

-

move

-

-

commandgetkeys-cluster setslot-

randomkey--

cluster slaves

-

-

-

-

readonly

-

-

-

-

readwrite

-

-

-

-

config set

-

-

-

-

-

-

configresetstat

-

-

-

-

-

-

debug
object

-

-

-

-

-

-

debug
segfault

-

-

-

-

-

-

flushall

-

-

-

-

-

-

flushdb

-

-

-

-

-

-

lastsave

-

-

-

-

-

-

monitor-©2013-2022 Tencent Cloud. All rights reserved.

clientsetnamecommandinfo
config get
configrewrite--Page 30 of 52

TencentDB for Redis

-

-

-

-

-

role

-

-

-

-

-

-

save

-

-

-

-

-

-

shutdown

-

-

-

-

-

-

slaveof

-

-

-

-

-

-

slowlog

-

-

-

-

-

-

sync

-

-

-

-

-

-

info

-

©2013-2022 Tencent Cloud. All rights reserved.

Page 31 of 52

TencentDB for Redis

Performance：

Last updated 2023-04-19 14:28:01

Specifications
Memory edition
Note
As a trial version, the 256 MB specification on v4.0 or v5.0 is only suitable for product verification in testing
environments. We don't recommend that you use it in production environments. It is available only in the following AZs:
Guangzhou (Zones 6 and 7), Shanghai (Zones 2, 3, 4 and 5), Beijing (Zones 1, 2, 3, 4, 5, 6, and 7), and Shenzhen
Finance (Zones 1, 2, and 3). Other 1 GB and above specifications can be smoothly downgraded to the 256 MB
specification.
v2.8 is unavailable currently, and v4.0 or later is recommended. To purchase v2.8, submit a ticket.
FeatureStandard Architecture

Compatible
Redis version

2.8

4.0, 5.0

6.2

4.0, 5.0

Memoryspecification

256 MB–64
GB

256 MB–64
GB

1 GB–64GB

2 GB–8 TB

Shard quantity

Not supported

QPS

Cluster Architecture

1, 3, 5, 8, 12, 16, 24, 32, 40, 48, 64, 80,
96, 128

80,000–80,000–80,000–100,000

100,000

100,000

Maximum

10,000 by

number ofconnections

default; up to
40,000Traffic limit

6.2

80,000–100,000/shard

10,000 by default; up to
40,00010,000/shard by default; up to
40,000/shard

10 MB/s–64
MB/s

528 MB/s–608 MB/s

288 MB/s–72 GB/s

Multidatabase

Supported

Supported

Supported

Supported

Mget and
Mset

Supported

Supported

Supported

Supported

Lua

Supported

Supported

Supported (crossslot access not

Supported (crossslot access not©2013-2022 Tencent Cloud. All rights reserved.

Page 32 of 52

TencentDB for Redis

supported)

supported)

Horizontal
scaling

Not supported

Not supported

Supported

Supported

Replicascaling

Not supported

Supported

Supported

Supported

Read/Write
separation

Not supported

Supported

Supported

Supported

GEO

Not supported

Supported

Supported

Supported

Replicaquantity1

1–5

Description of the CPU core quantity
To ensure the stable operations of the system, each node is assigned with 2-core CPU, one of which is used toprocess the backend tasks.

CKV edition
FeatureStandard Architecture

Cluster Architecture

3.2

3.2

4 GB–384 GB

12 GB–48 TB

Shard quantity

-

3–128

QPS

80,000–120,000

Tens of millions

number ofconnections

12,000–24,000

12,000–24,000/shard

Traffic limit

16 MB/s–256 MB/s

72 MB/s–32 GB/s

Multi-database

Supported

Supported

Mget and Mset

Supported

Supported

Lua

Supported

Limited support (to use Lua in the cluster edition, you need

Compatible Redis
versionMemoryspecification

Maximum

to make sure that the keys accessed in the Lua script are©2013-2022 Tencent Cloud. All rights reserved.

Page 33 of 52

TencentDB for Redisin the same slot, and the key field must be included in
the command parameters)
Horizontal scaling

Not supported

Supported

Replica scaling

Not supported

Not supported

Read/Write
separation

Not supported

Not supported

GEO

Supported

Supported

Traffic and connections
Memory edition
Specification (GB)Maximum number of connections

Maximum throughput (MB/s)

0.25

3,000

10

1

40,00016

240,00024

440,00024

840,00024

1240,00032

1640,00032

20

40,00048

24

40,00048

32

40,00048

40

40,00064

48

40,00064

60

40,00064

Maximum number of connections

Maximum throughput (MB/s)

CKV edition
Specification (GB)©2013-2022 Tencent Cloud. All rights reserved.

Page 34 of 52

TencentDB for Redis

4

10,00024

8

10,00024

16

10,00032

24

10,00032

32

10,00032

48

18,00064

64

18,0006480

18,00064

96

18,00064

128

24,000128

160

24,000128

192

24,000128

256

24,000256

320

24,000256

384

24,000256

Cluster edition connections = number of connections per shard number of shards;
Cluster edition throughput = shard throughput number of shards
Notes
After scaling, legacy instances capable of up to 9,000 connections will be capable of 10,000 connections.

Performance Data
Performance references
The time needed to execute Redis commands varies. Businesses use different database commands in theirproduction environments; therefore, the corresponding performance values will also vary. The test results listed here
are obtained with specified parameters and are for your reference only. Conduct tests in your actual businessenvironment for more accurate results.
Single-node test performance©2013-2022 Tencent Cloud. All rights reserved.

Page 35 of 52

TencentDB for Redis

Redis Instance Specification

Connections

QPS

Memory Edition (Standard Architecture) 8
GB10,00080,000–100,000

Memory Edition (Cluster Architecture) 8 GB
(single-shard)

10,00080,000–100,000

CKV Edition (Standard Architecture) 8 GB

12,00080,000–120,000

Cluster architecture test performance
Memory Edition (Cluster Architecture) performance = Memory Edition (Standard Architecture) performance numberof shards
CKV Edition (Cluster Architecture) performance = CKV Edition (Standard Architecture) performance number ofshardsTest method
Test environment
Test Client CVM
Instances

CVM Cores

CVM Memory

RegionRedis Instance Specification

3

2

8 GB

Guangzhou
Zone 2

Memory Edition (Standard
Architecture) 8 GB

3

2

8 GB

Guangzhou
Zone 2CKV Edition (Standard
Architecture) 8 GB

Test parameters©2013-2022 Tencent Cloud. All rights reserved.

Page 36 of 52

TencentDB for Redis

redis-benchmark -h 10.66.187.x -p 6379 -a crs-1znib6aw:chen2016 -t set -c 3500 -d 1
redis-benchmark -h 10.66.187.x -p 6379 -a crs-1z5536aw:chen2016 -t set -c 3500 -d 1
redis-benchmark -h 10.66.187.x -p 6379 -a crs-090rjlih:1234567 -t set -c 3500 -d 12

QPS calculation
Sum of the QPS values of three pressure test clients (tested by redis-benchmark).

©2013-2022 Tencent Cloud. All rights reserved.

Page 37 of 52

TencentDB for Redis

Read/Write Separation：

Last updated 2021-03-17 12:01:51
TencentDB for Redis supports read-write separation for business scenarios with more reads but less writes, which
can well cope with read requests concentrating on frequently read data. It supports up to 1-master 5-replica mode tooffer 5x read performance.

How It Works
Memory Edition
Read/write separation principle: TencentDB for Redis v4.0 and later in standard architecture or cluster architecture
implement automatic read/write separation at the Proxy layer.
Read-write separation weight: after read/write separation is enabled, Proxy will enable access by directing write
requests to the master node only and distributing read requests evenly on replica nodes.

©2013-2022 Tencent Cloud. All rights reserved.

Page 38 of 52

TencentDB for RedisCKV Edition
Read/write separation principle: CKV Edition inherently supports the read/write separation architecture. All
requests are distributed to nodes in clusters through the CLB gateway, and each node has the global slot routing
information. After read/write separation is enabled for a node, if the read key hits it, the data will be read directly andreturned; otherwise, the request will be forwarded to the corresponding node according to the routing information,
which will read the data and return it to this node for final return to the client.
Read/write separation weight: requests in the CKV Edition are distributed by CLB, so read and write weights areevenly distributed according to the quadruple of the TCP connection (source IP, source port, destination IP, and©2013-2022 Tencent Cloud. All rights reserved.

Page 39 of 52

TencentDB for Redis

destination port).

©2013-2022 Tencent Cloud. All rights reserved.

Page 40 of 52

TencentDB for Redis

Multi-AZ Deployment：

Last updated 2023-10-20 10:51:18
You can now deploy TencentDB for Redis master and replica nodes in different availability zones (AZs) of the same
region. Multi-AZ deployed instances have higher availability and better disaster recovery capability than single-AZ
deployed instances.
Single-AZ deployed instance: Host- and rack-level disaster recovery
Multi-AZ deployed instance: Host-, rack-, and AZ-level disaster recovery

Deployment Architecture

Description:
LB (Load Balancer): A TencentDB for Redis instance in standard architecture or cluster architecture has at least threeproxies which need to be accessed through LB.
VIP: A multi-AZ deployed instance has only one VIP. You can use this VIP to access all nodes of the instancedeployed in the region. Master-replica switches of the instance will not change its VIP.
Proxy: The proxy access service implements the request routing to distribute the data requests of the users.
If read-only replica is enabled, each instance has at least three proxies. For a standard architecture instance, thenumber of proxies = 3 + (the number of replicas -1); for a cluster architecture instance, the number of proxies = Max©2013-2022 Tencent Cloud. All rights reserved.

Page 41 of 52

TencentDB for Redis[the number of shards the number of replicas; shard quantity 1.5 (rounded up)]
If read-only replica is not enabled, for a standard architecture instance, the number of proxies is 3; for a clusterarchitecture instance, the number of proxies is shard quantity * 1.5 (rounded up).
Master (Group): "Master" refers to the master node of a TencentDB for Redis instance in standard architecture;"Master Group" refers to the master nodes of all shards of a TencentDB for Redis instance in cluster architecture.
Replica (Group): "Replica" refers to the replica nodes of a TencentDB for Redis instance in standard architecture;"Replica Group" refers to the collection of replica nodes, each of which comes from a different shard of a TencentDB
for Redis instance in the cluster architecture. For a cluster architecture instance, the replicas of a shard are divided
into multiple Replica Groups so that these Replica Groups can be deployed in different AZs.
Master AZ: The master AZ refers to the AZ where the master node resides. Unless manually changed in the console,
the master AZ will remain the same. If the master node fails, it may be temporarily switched to a replica AZ, and will be
automatically switched back to the master AZ in a few minutes once certain conditions are met. This switching backprocess won't affect your business unless your business uses block commands, such as blpop or blpush .

Failover (HA)
Detect failed nodes: TencentDB for Redis in standard architecture or cluster architecture adopts the same cluster
management mechanism as the Redis Cluster, which uses the Gossip protocol to detect the status of nodes in acluster. The cluster-node-timeout parameter is used to specify the maximum amount of time a Redis cluster
node can be unavailable, without it being considered as failing. We recommend that you set this parameter to its
default value (15s) and do not change it. For more information, see Scale with Redis Cluster.
Promote a replica to master: TencentDB for Redis adopts a failover mechanism different from that of Redis Cluster,which gives priority to promoting replicas in the master AZ to reduce access delay of the master AZ. The details are as
follows:
Promote the replica if it has the latest data.
Promote the replica in the master AZ if all replicas have the same data.

Cross-AZ Access
Instance with read-only replica disabled
Read/Write separation disabled (that is, replicas can be written to and read from): Write/read requests in a replica AZ
are routed by proxy to the master node, and the master node synchronizes with replica nodes to ensure consistent
data across all nodes. In this process, only one cross-AZ access happens.

Instance with read-only replica enabled©2013-2022 Tencent Cloud. All rights reserved.

Page 42 of 52

TencentDB for Redis

Read/write separation enabled (that is, replicas can only be read from): Write requests are routed by proxy to themaster node, but read requests are routed to the replica node in the same AZ as the proxy, so that read requests can
get responded by the nearest node.
Note
There is a 2–5 ms delay during cross-AZ access.

Recommended Deployment Solution
Two-AZ deployment
Deploy the master node and one replica node in the master AZ, and two replica nodes in the replica AZ. Both AZs,
each of which has two nodes, are accessed through LB. If one node in an AZ fails, the read requests can beprocessed by the other node in the AZ. If an AZ fails, the other AZ is still highly available. This solution is suitable for
scenarios where high availability is required and delay is sensitive.

Three-AZ deployment
Deploy the master node in the master AZ, one replica node in replica AZ 1, and one replica node in replica AZ 2. If one
node or one AZ fails, the whole architecture still has cross-AZ high availability. This solution is is suitable for scenarios
where extremely high availability is required but delay is insensitive.

©2013-2022 Tencent Cloud. All rights reserved.

Page 43 of 52

TencentDB for Redis

Relevant Operations
For more information on how to configure and view multi-AZ deployment in the TencentDB for Redis console, see
Configuring Multi-AZ Deployment.
For more information on how to upgrade the deployment from single-AZ to multi-AZ in the TencentDB for Redis
console, see Upgrading to Multi-AZ Deployment.
For more information on how to enable and disable read/write separation in the TencentDB for Redis console, see
Enabling/Disabling Read/Write Separation.
Both multi-AZ and single-AZ deployed TencentDB for Redis instances can be accessed by a VIP. For more
information, see Accessing Multi-AZ Deployed Instances.
TencentDB for Redis supports auto-failover to ensure the high availability of database service. For more information,
see Failure Simulation.
Multi-AZ deployed TencentDB for Redis instances support auto-failback. For more information, see Auto-Failback.
For a multi-AZ deployed TencentDB for Redis instance, you can manually promote a replica node (group) in a specific
AZ to master node (group) and the AZ will be automatically promoted to master AZ. For more information, see
Manually Promoting to Master Node (Group).
To reduce the latency of accessing a multi-AZ deployed TencentDB for Redis instance, you can read local nodes only.
For more information, see Reading Local Nodes Only.

©2013-2022 Tencent Cloud. All rights reserved.

Page 44 of 52

TencentDB for Redis

Regions and AZs：

Last updated 2023-06-26 14:54:16

Regions
Overview
A region is the physical location of an IDC. In Tencent Cloud, regions are fully isolated from each other, ensuringcross-region stability and fault tolerance. When purchasing Tencent Cloud services, we recommend selecting theregion closest to your end users to minimize access latency and improve download speed.

Characteristics
The networks of different regions are fully isolated from each other, and Tencent Cloud services in different regions
cannot communicate using private networks by default.
Tencent Cloud services in different VPCs can communicate with each other through Cloud Connect Network that isfaster and steadier.
Notes
Shenzhen/Shanghai Finance Zones are tailor-made AZs for compliance with regulatory requirements in thefinance industry and feature high security and isolation. Currently, they are available for CVM, finance database, Redisstorage, and face recognition services. They can be activated by verified financial customers by contacting customer
service.

AZs
Overview
An availability zone (AZ) is a physical IDC of Tencent Cloud with independent power supply and network in the same
region. It can ensure business stability, as failures (except for major disasters or power failures) in one AZ are isolated
without affecting other AZs in the same region. By starting an instance in an independent AZ, users can protect theirapplications from being affected by a single point of failure.

Characteristics
Tencent Cloud services in the same VPC are interconnected via the private network, which means they cancommunicate using private IPs, even if they are in different AZs of the same region.
Notes
Private network interconnection refers to the interconnection of resources under the same account. Resources under
different accounts are completely isolated on the private network.

©2013-2022 Tencent Cloud. All rights reserved.

Page 45 of 52

TencentDB for Redis

List of Regions and AZs
Notes
Resources available in different regions and AZs may be sold out and become unavailable, and previously sold-out
resources may be replenished. The resource availability will be assessed and adjusted based on the actual businessusage as displayed on the purchase page in the console.

China
RegionSouth China (Guangzhou)
ap-guangzhou

South China (Shenzhen Finance)
ap-shenzhen-fsi

East China (Shanghai)
ap-shanghai

AZ

ZoneIdGuangzhou Zone 1
ap-guangzhou-1

100001

Guangzhou Zone 2
ap-guangzhou-2

100002

Guangzhou Zone 3
ap-guangzhou-3

100003

Guangzhou Zone 4
ap-guangzhou-4

100004

Guangzhou Zone 6
ap-guangzhou-6

100006

Guangzhou Zone 7
ap-guangzhou-7

100007

Shenzhen Finance Zone 1 (only financial institutions andenterprises can contact us to apply for activation)
ap-shenzhen-fsi-1

110001

Shenzhen Finance Zone 2 (only financial institutions andenterprises can contact us to apply for activation)
ap-shenzhen-fsi-2

110002

Shenzhen Finance Zone 3 (only financial institutions andenterprises can contact us to apply for activation)
ap-shenzhen-fsi-3

110003

Shanghai Zone 1
ap-shanghai-1

200001

Shanghai Zone 2
ap-shanghai-2

200002©2013-2022 Tencent Cloud. All rights reserved.

Page 46 of 52

TencentDB for Redis

Shanghai Zone 3
ap-shanghai-3

East China (Shanghai Finance)
ap-shanghai-fsi

East China (Nanjing)
ap-nanjingNorth China (Beijing)
ap-beijing

200003

Shanghai Zone 4
ap-shanghai-4

200004

Shanghai Zone 5
ap-shanghai-5

200005

Shanghai Zone 7
ap-shanghai-7

200007

Shanghai Zone 8
ap-shanghai-8

200008

Shanghai Finance Zone 1 (only financial institutions andenterprises can contact us to apply for activation)
ap-shanghai-fsi-1

700001

Shanghai Finance Zone 2 (only financial institutions andenterprises can contact us to apply for activation)
ap-shanghai-fsi-2

700002

Shanghai Finance Zone 3 (only financial institutions andenterprises can contact us to apply for activation)
ap-shanghai-fsi-3

700003

Nanjing Zone 1
ap-nanjing-1

330001Nanjing Zone 2
ap-nanjing-2

330002

Nanjing Zone 3
ap-nanjing-3

330003Beijing Zone 1
ap-beijing-1

800001

Beijing Zone 2
ap-beijing-2

800002Beijing Zone 3
ap-beijing-3
Beijing Zone 4
ap-beijing-4©2013-2022 Tencent Cloud. All rights reserved.

800003800004

Page 47 of 52

TencentDB for Redis

Beijing Zone 5
ap-beijing-5
Beijing Zone 6
ap-beijing-6

North China (Beijing Finance)
ap-beijing-fsi

Southwest (Chengdu)
ap-chengdu

Southwest (Chongqing)
ap-chongqing

800005800006

Beijing Zone 7
ap-beijing-7

800007

Beijing Finance Zone 1 (only financial institutions andenterprises can contact us to apply for activation)
ap-beijing-fsi-1

460001Chengdu Zone 1
ap-chengdu-1

160001Chengdu Zone 2
ap-chengdu-2

160002Chongqing Zone 1
ap-chongqing-1

190001

Hong Kong Zone 1 (Hong Kong nodes cover services in
the China regions of Hong Kong, Macao, and Taiwan)
ap-hongkong-1

300001

Hong Kong/Macao/Taiwan (China
Region) (Hong Kong, China)

Hong Kong Zone 2 (Hong Kong nodes cover services in
the China regions of Hong Kong, Macao, and Taiwan)

ap-hongkong

ap-hongkong-2
Hong Kong Zone 3 (Hong Kong nodes cover services in
the China regions of Hong Kong, Macao, and Taiwan)
ap-hongkong-3

300002300003

Other countries and regions
RegionAZ

ZoneIdSoutheast Asia Pacific(Singapore)
ap-singapore

Singapore Zone 1 (Singapore nodes cover services inSoutheast Asia)
ap-singapore-1

900001

Singapore Zone 2 (Singapore nodes cover services inSoutheast Asia)
ap-singapore-2

900002Singapore Zone 3 (Singapore nodes cover services in

900003©2013-2022 Tencent Cloud. All rights reserved.

Page 48 of 52

TencentDB for Redis

Southeast Asia)
ap-singapore-3

Southeast Asia (Jakarta)
ap-jakarta

Singapore Zone 4 (Singapore nodes cover services inSoutheast Asia)
ap-singapore-4

900004

Jakarta Zone 1 (Jakarta nodes cover services in SoutheastAsia)
ap-jakarta-1

720001

Jakarta Zone 2 (Jakarta nodes cover services in Southeast
Asia)

720002

ap-jakarta-2

Southeast Asia Pacific (Bangkok)
ap-bangkok

Southern Asia Pacific (Mumbai)
ap-mumbai

Bangkok Zone 1 (Bangkok nodes cover services inSoutheast Asia)
ap-bangkok-1

230001

Bangkok Zone 2 (Bangkok nodes cover services inSoutheast Asia)
ap-bangkok-2

230002

Mumbai Zone 1 (Mumbai nodes cover services in SouthAsia)
ap-mumbai-1

210001

Mumbai Zone 2 (Mumbai nodes cover services in SouthAsia)
ap-mumbai-2

210002Seoul Zone 1 (Seoul nodes cover services in Northeast
Northeast Asia (Seoul)
ap-seoul

Northeast Asia (Tokyo)
ap-tokyoWest US (Silicon Valley)Asia)
ap-seoul-1

180001Seoul Zone 2 (Seoul nodes cover services in NortheastAsia)
ap-seoul-2

180002

Tokyo Zone 1 (Tokyo nodes cover services in Northeast
Asia)
ap-tokyo-1

250001

Tokyo Zone 2 (Tokyo nodes cover services in Northeast
Asia)
ap-tokyo-2

250002

Silicon Valley Zone 1 (Silicon Valley nodes cover services in

150001©2013-2022 Tencent Cloud. All rights reserved.

Page 49 of 52

TencentDB for Redisna-siliconvalley

West US)na-siliconvalley-1
Silicon Valley Zone 2 (Silicon Valley nodes cover services inWest US)na-siliconvalley-2
Virginia Zone 1 (Virginia nodes cover services in East US)

East US (Virginia)
na-ashburnna-ashburn-1

150002220001

Virginia Zone 2 (Virginia nodes cover services in East US)
na-ashburn-2

220002

Toronto Zone 1 (Toronto nodes cover services in North
America)na-toronto-1

400001Frankfurt Zone 1 (Frankfurt nodes cover services in
Europe)eu-frankfurt-1

170001Frankfurt Zone 2 (Frankfurt nodes cover services in
Europe)eu-frankfurt-2

170002EuropeNodes cover services in Europe

240001

South America (São Paulo)
sa-saopauloSão Paulo Zone 1 (São Paulo nodes cover services inSouth America)
sa-saopaulo-1

740001

North America (Toronto)
na-toronto

Europe (Frankfurt)
eu-frankfurt

Selection of Regions and AZs
When you purchase Tencent Cloud services, we recommend that you select the region closest to your end users tominimize access latency and improve download speed.

©2013-2022 Tencent Cloud. All rights reserved.

Page 50 of 52

TencentDB for Redis

Relevant Concepts：

Last updated 2019-10-16 13:31:55
TencentDB for Redis generally involves the following concepts:
Instance: A database environment running independently in Tencent Cloud. One database instance can containmultiple user-created databases.
VPC: A custom virtual network space that is logically isolated from other resources.
Security group: Security access control to Redis instances by specifying IP, protocol, and port rules for instanceaccess.
Region and availability zone: The physical location of a Redis instance and other resources.
Tencent Cloud Console: Web-based UIs.
Project: A feature developed to enable developers to better manage Tencent Cloud products based on the concept ofprojects. You can implement project management by assigning different Tencent Cloud products to different projects.
Read-write separation: TencentDB for Redis supports switching Read-Write separation on or off. It targets atbusiness scenarios with more Reads and less Writes, which can well cope with Read requests concentrating on
hotspot data. It supports up to 1-master 5-slave mode to offer 5x Read performance scalablity.

©2013-2022 Tencent Cloud. All rights reserved.

Page 51 of 52

TencentDB for Redis

Relevant Products：

Last updated 2019-09-09 11:39:54
TencentDB for Redis generally involves the following products:
You can deploy your computing services by purchasing Cloud Virtual Machine (CVM) instances. For more
information, see CVM.
You can use Cloud Monitor to monitor the running status of your TencentDB for Redis instances. For more
information, see Cloud Monitor.
You can write code to call TencentCloud APIs to access Tencent Cloud products and services. For more information,
see the TencentCloud API documentation.

©2013-2022 Tencent Cloud. All rights reserved.

Page 52 of 52