- Requires a self-managed network security system. It is expensive and difficult to
build such a system.
- Comes with risks of data leaks due to security vulnerabilities in the default access
configuration of open source Redis.
- Does not have an account authentication system.
|In-process protection: implements SSL encryption. For more information, see Configure SSL encryption for an ApsaraDB for Redis instance.
||In-process protection: requires a third-party tool to implement SSL encryption.
|Post audit: supports audit logs. For more information, see Query audit logs.
||Post audit: does not provide the auditing feature.
|Backup and restoration
||Performance-enhanced instances of ApsaraDB for Redis Enhanced Edition (Tair) support
the data flashback feature that allows you to restore data to a specific point in
time. For more information about performance-enhanced instances, see Performance-enhanced instances. For more information about the data flashback feature, see Use data flashback to restore data by point in time.
||Only full data restoration is supported.
- Supports more than ten groups of metrics and a minimum monitoring frequency of 5 seconds.
For more information, see Monitoring metrics.
- Supports alert settings. For more information, see Alert settings.
- Allows you to create instances of different architectures based on your business requirements
and change specifications.
- Supports big key analytics based on snapshots to ensure high accuracy and prevent
performance loss. For more information, see Use the cache analysis feature to display details about big keys.
- Requires a more sophisticated third-party monitoring tool to monitor services.
- Stops services when you change the specifications or architecture. The operation to
change the specifications or architecture is complex.
- Supports big key analytics based on sampling, which provides limited precision.
|Deployment and scaling
||Supports instant activation and elastic scaling.
||Requires a long period of time to complete hardware procurement, hosting of data centers,
and machine deployment. You must manage node relationships when you add nodes.
|High availability (HA)
- Allows you to deploy a high-availability architecture in Sentinel mode in a data center.
- Allows you to deploy a zone-disaster recovery architecture in Sentinel mode.
- Uses the Sentinel mode to ensure high availability. The decision-making efficiency
is low during peak hours and the cost is high. Split-brain issues may occur and affect
- Provides performance-enhanced instances based on the multi-threading model. For more
information, see Performance-enhanced instances. The performance of a performance-enhanced instance is three times that of a standard
instance with the same specifications.
- Provides storage-optimized and persistent memory-optimized instances to support large-capacity
storage and command-level persistence. For more information about storage-optimized
and persistent memory-optimized instances, see Storage-optimized instances and Persistent memory-optimized instances.
- Clusters of Redis 6.0 or later support multiple I/O threads to enhance performance.
The performance of a Redis cluster can be increased by up to twice the original performance.
However, the CPU utilization is high.
- Uses a storage service such as SSDB or Pika as the persistent storage. However, these
storage services are not fully compatible with the Redis protocol, and they can manage
hot and cold data only at the key level. It is expensive to transfer big keys between
the memory and disks in these storage services, and these services are also difficult