For enhanced experience, Tair (Redis OSS-compatible) read/write splitting instances deployed in classic mode are no longer available for purchase starting August 12, 2024.
End-of-sale date
August 12, 2024
Impacts and suggestions
Existing instances: If you purchased classic read/write splitting instances, you can continue to use, renew, and modify the configurations of the instances without issues.
New instances: When you make new purchases, you cannot create classic read/write splitting instances.
We recommend that you select cloud-native read/write splitting instances, which support more read replicas and provide better flexibility. The following table describes the differences between cloud-native and classic read/write splitting instances.
Comparison item | Cloud-native deployment mode | Classic deployment mode |
Number of read replicas | The number of read replicas in a read/write splitting instance is adjustable within the range of 1 to 9. | The number of read replicas can be set to 1, 3, or 5. |
Replica node | All read replicas except the master node can be used as replica nodes for failover. You do not need to separately configure replica nodes. | An additional replica node is required for failover. This node does not provide external services. |
Multi-zone deployment | Multi-zone proximity access is supported. | Multi-zone proximity access is not supported. Only replica nodes can be deployed in secondary zones. |
FAQ
Can I change a classic read/write splitting instance to a cloud-native read/write splitting instance?
No, you cannot change a classic read/write splitting instance to a cloud-native read/write splitting instance. You must create a cloud-native read/write splitting instance, use Data Transmission Service (DTS) to migrate the data of the classic instance to the cloud-native instance, and then modify the application code to connect to the new instance. For information about how to migrate data, see Configure one-way data migration between ApsaraDB for Redis instances.
The current read/write splitting instance is a Redis Open-Source Edition 4.0 instance, but cloud-native instances do not support Redis Open-Source Edition 4.0. How do I migrate data from the current instance to a cloud-native instance?
Redis Open-Source Edition 5.0 is backward compatible with all features of Redis Open-Source Edition 4.0. You can create a Redis Open-Source Edition 5.0 read/write splitting instance that is deployed in cloud-native mode, and then use DTS to migrate data.