What's New
The following tables describe the features released in each DCS version and corresponding documentation updates. New features will be successively launched in each region.
June 2025
No. |
Feature |
Description |
Phase |
Document |
---|---|---|---|---|
1 |
Enabling public access to Redis |
Public access can be enabled using Elastic Load Balance (ELB) for single-node, master/standby, read/write splitting, and Proxy Cluster DCS Redis instances. |
Open beta testing |
Enabling Public Access to Redis and Obtaining the Access Addresses |
November 2024
No. |
Feature |
Description |
Phase |
Document |
---|---|---|---|---|
1 |
DCS Redis 7.0 |
DCS Redis 7.0 is in OBT. |
Open beta testing |
April 2024
No. |
Feature |
Description |
Phase |
Document |
---|---|---|---|---|
1 |
Adjusting Redis instance bandwidth |
Bandwidth can be separately purchased for DCS Redis 4.0 and later instances. |
Commercial use |
|
2 |
Stopping a Redis instance |
DCS Redis 4.0 and later instances support instance stop. When an instance is stopped, data reading or writing is stopped so that the instance cannot be modified, configured, backed up, or migrated. You can neither change the password nor analyze the cache. |
Commercial use |
September 2023
No. |
Feature |
Description |
Phase |
Document |
---|---|---|---|---|
1 |
DCS Redis 6.0 |
Single-node and master/standby DCS Redis 6.0 instances are available. |
Commercial use |
June 2023
No. |
Feature |
Description |
Phase |
Document |
---|---|---|---|---|
1 |
Enabling multi-AZ for a Cluster instance |
By enabling multi-AZ for a single-AZ cluster instance, you can deploy the instance in two AZs for DR. |
Commercial use |
December 2022
No. |
Feature |
Description |
Phase |
Document |
---|---|---|---|---|
1 |
Managing sessions |
You can view the clients connected to an instance and disconnect them. This feature is not available in all regions. |
Commercial use |
March 2022
No. |
Feature |
Description |
Phase |
Document |
---|---|---|---|---|
1 |
Read/write splitting DCS Redis instances |
Proxy-based read/write splitting instances are provided for high-concurrency scenarios where there are more read requests than write requests. A maximum of one master and five replicas. |
Commercial use |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.