- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Operation Overview
- Access Management
- SDK Connection
- Daily Instance Operation
- Viewing Instance Information
- Assigning Instance to Project
- Editing Instance Tag
- Setting Maintenance Time
- Changing Instance Specification
- Adjusting the Number of Connections
- Enabling/Disabling Read/Write Separation
- Clearing Instances
- Returning and Isolating Instance
- Restoring Isolated Instance
- Eliminating Instance
- Instance Upgrade
- Node Management
- Multi-AZ Deployment Management
- Backup and Restoration
- Data Migration
- Account and Password
- Parameter Configuration
- Slow Log
- Network and Security
- Monitoring and Alarms
- Event Management
- Global Replication
- Performance Optimization
- Sentinel Mode
- Development Guidelines
- Command Compatibility
- Troubleshooting
- Best Practices
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- AddReplicationInstance
- AllocateWanAddress
- ChangeInstanceRole
- ChangeMasterInstance
- CleanUpInstance
- ClearInstance
- CloseSSL
- CreateInstanceAccount
- CreateReplicationGroup
- DeleteInstanceAccount
- DeleteReplicationInstance
- DescribeAutoBackupConfig
- DescribeBandwidthRange
- DescribeInstanceAccount
- DescribeInstanceDTSInfo
- DescribeInstanceZoneInfo
- DescribeInstances
- DescribeProxySlowLog
- DescribeSlowLog
- DescribeTendisSlowLog
- DestroyPostpaidInstance
- DestroyPrepaidInstance
- DisableReplicaReadonly
- EnableReplicaReadonly
- InquiryPriceCreateInstance
- InquiryPriceUpgradeInstance
- KillMasterGroup
- ModifyAutoBackupConfig
- ModifyInstance
- ModifyInstanceAccount
- ModifyInstanceReadOnly
- ModifyMaintenanceWindow
- ModifyNetworkConfig
- OpenSSL
- ReleaseWanAddress
- RenewInstance
- ResetPassword
- StartupInstance
- SwitchProxy
- UpgradeInstanceVersion
- UpgradeProxyVersion
- UpgradeSmallVersion
- UpgradeVersionToMultiAvailabilityZones
- DescribeCommonDBInstances
- ChangeReplicaToMaster
- CloneInstances
- CreateInstances
- DescribeInstanceDealDetail
- DescribeInstanceNodeInfo
- DescribeInstanceShards
- DescribeMaintenanceWindow
- DescribeParamTemplateInfo
- DescribeReplicationGroup
- DescribeSSLStatus
- DescribeTaskInfo
- DescribeTaskList
- ModfiyInstancePassword
- RemoveReplicationInstance
- UpgradeInstance
- DescribeInstanceEvents
- ModifyInstanceAvailabilityZones
- ModifyInstanceEvent
- SwitchAccessNewInstance
- DescribeInstanceSupportFeature
- Parameter Management APIs
- Other APIs
- Region APIs
- Monitoring and Management APIs
- Backup and Restoration APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Glossary
- Contact Us
- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Operation Overview
- Access Management
- SDK Connection
- Daily Instance Operation
- Viewing Instance Information
- Assigning Instance to Project
- Editing Instance Tag
- Setting Maintenance Time
- Changing Instance Specification
- Adjusting the Number of Connections
- Enabling/Disabling Read/Write Separation
- Clearing Instances
- Returning and Isolating Instance
- Restoring Isolated Instance
- Eliminating Instance
- Instance Upgrade
- Node Management
- Multi-AZ Deployment Management
- Backup and Restoration
- Data Migration
- Account and Password
- Parameter Configuration
- Slow Log
- Network and Security
- Monitoring and Alarms
- Event Management
- Global Replication
- Performance Optimization
- Sentinel Mode
- Development Guidelines
- Command Compatibility
- Troubleshooting
- Best Practices
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- AddReplicationInstance
- AllocateWanAddress
- ChangeInstanceRole
- ChangeMasterInstance
- CleanUpInstance
- ClearInstance
- CloseSSL
- CreateInstanceAccount
- CreateReplicationGroup
- DeleteInstanceAccount
- DeleteReplicationInstance
- DescribeAutoBackupConfig
- DescribeBandwidthRange
- DescribeInstanceAccount
- DescribeInstanceDTSInfo
- DescribeInstanceZoneInfo
- DescribeInstances
- DescribeProxySlowLog
- DescribeSlowLog
- DescribeTendisSlowLog
- DestroyPostpaidInstance
- DestroyPrepaidInstance
- DisableReplicaReadonly
- EnableReplicaReadonly
- InquiryPriceCreateInstance
- InquiryPriceUpgradeInstance
- KillMasterGroup
- ModifyAutoBackupConfig
- ModifyInstance
- ModifyInstanceAccount
- ModifyInstanceReadOnly
- ModifyMaintenanceWindow
- ModifyNetworkConfig
- OpenSSL
- ReleaseWanAddress
- RenewInstance
- ResetPassword
- StartupInstance
- SwitchProxy
- UpgradeInstanceVersion
- UpgradeProxyVersion
- UpgradeSmallVersion
- UpgradeVersionToMultiAvailabilityZones
- DescribeCommonDBInstances
- ChangeReplicaToMaster
- CloneInstances
- CreateInstances
- DescribeInstanceDealDetail
- DescribeInstanceNodeInfo
- DescribeInstanceShards
- DescribeMaintenanceWindow
- DescribeParamTemplateInfo
- DescribeReplicationGroup
- DescribeSSLStatus
- DescribeTaskInfo
- DescribeTaskList
- ModfiyInstancePassword
- RemoveReplicationInstance
- UpgradeInstance
- DescribeInstanceEvents
- ModifyInstanceAvailabilityZones
- ModifyInstanceEvent
- SwitchAccessNewInstance
- DescribeInstanceSupportFeature
- Parameter Management APIs
- Other APIs
- Region APIs
- Monitoring and Management APIs
- Backup and Restoration APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Glossary
- Contact Us
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 select the 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 database environments 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 and performance 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 Performance
High throughput: The Standard Edition has a performance of up to 100,000+ QPS for concurrent response, and the Cluster Edition supports up to tens of millions of QPS as the number of shards increases. Their ultra-high performance can perfectly meet the needs in most business scenarios ranging from gaming, mobile apps to advertising and ecommerce.
Low latency: TencentDB for Redis delivers stable low-latency response, where 99% requests can be responded to within 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 the read 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.
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, and performance 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 load balancing.
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. This solves 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 the master, 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 storage engine 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 across accounts, 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 running status of your instances and quickly troubleshoot problems.
**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 optimization suggestions. This helps you promptly optimize the database performance.
Management APIs: TencentDB for Redis offers a complete set of management APIs to implement diverse self-service 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 terms of 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 |
Cost | For a self-built database, storage servers are costly. If you want a high-availability master/replica instance, you will have to purchase three servers, which may cause resource redundancy and waste. In addition, you need to recruit professional database administrators, which also means high labor costs. | With TencentDB, you don't have to invest in hardware and software. You have a variety of specification options to choose from. You can apply for necessary resources based on your actual business conditions to maximize the resource utilization. In addition, you can use the free-of-charge features such as management, backup, clone, monitoring, and alarm. In conclusion, TencentDB has a higher cost effectiveness with similar resource costs. |
HA | > 60s | < 60s |
Availability | You need to fix failures and build master/replica cluster architecture on your own. | Hot backup is supported based on two or more servers, with automatic disaster recovery, failover, and imperceptible migration features available, delivering a 99.95% availability. Read preference from replica databases is supported to ensure high concurrent read capability. |
Scaling | Business scaling is much slower because you must do the tedious tasks on your own, like procuring hardware, hosting data centers, and redeploying applications. In addition, double write and data migration cause momentary disconnections during switch and involve high data risks. | Scaling can be performed quickly as needed, with no momentary disconnections, downtime, or read-only access. |
Read/write separation | Separate development is required. | Automatic read/write separation is supported and can be enabled/disabled based on the business needs. |
Isolation | CPU and memory isolation | CPU, memory, traffic, and connection isolation |
Multi-account | Not supported | Supported |
Blocklist | Not supported | High-risk commands can be disabled. |
Monitoring | Only a few monitoring metrics are available, which are collected by the server. | More than 30 metrics for clusters and nodes are available, including unique ones for latency, traffic, big key, and hot key. Alarms can be triggered for them, so you can perform Ops tasks proactively to prevent risks. |
Yes
No
Was this page helpful?