This topic describes the lifecycle of a Tair (Redis OSS-compatible) instance, which includes all operations from instance creation (purchase) to release or unsubscription.
Lifecycle
Figure 2. Lifecycle
Performing operations on an instance changes its status and may cause certain effects, such as transient connections that last for a few seconds. For more information, see Instance statuses and their effects.
Operation | Description |
Tair (Redis OSS-compatible) is available in two editions: Tair (Enterprise Edition) and Redis Open-Source Edition. Tair (Enterprise Edition) provides multiple instance series: memory-optimized, persistent memory, and disk-based. You can create an instance that meets your business requirements. | |
You can change the specifications, architecture, and type of an instance to meet various performance and compatibility requirements. | |
An instance with more shards delivers better overall performance. You can adjust the number of shards based on your performance requirements. | |
Enable read/write splitting | If read traffic is high and exceeds the performance limit of a node, you can enable read/write splitting. After this feature is enabled, the instance automatically detects and forwards read and write requests without requiring changes to your application code. This is ideal for scenarios with high concurrency for reads and writes. |
You can increase the number of replica nodes to improve the disaster recovery capability of the instance. | |
If an instance runs out of connections or has performance issues, you can restart the instance to release all connections. | |
You can upgrade the major version of a Redis Open-Source Edition instance, for example, from Redis 5.0-compatible to 7.0-compatible, to use the features of the new version. For more information, see New features and compatibility of major versions of Redis Open-Source Edition. | |
Tair (Redis OSS-compatible) continuously optimizes its kernel, fixes security vulnerabilities, and improves service stability. You can regularly check for and upgrade to the latest minor version. | |
The Cloud-native deployment mode is compatible with newer Redis versions and provides more flexible architecture configurations. You can convert an existing Classic instance to a Cloud-native instance. | |
You can release idle pay-as-you-go instances to save resources. | |
The recycle bin stores expired, overdue, and released instances. In the recycle bin, you can renew and unlock, recreate, or permanently destroy these instances. |