This topic compares the features of ApsaraDB for Redis Enhanced Edition (Tair) and Community Edition.
Key features and applicable scenarios
| Category | ApsaraDB for Redis Enhanced Edition (Tair) | ApsaraDB for Redis Community Edition | |
|---|---|---|---|
| Performance-enhanced instances | Hybrid-storage instances | ||
| Key features | Provides higher performance and more data structures to simplify development and improve the efficiency of data processing and storage. | Reduces costs and ensures the performance for hot data access. | Compatible with open source Redis databases and provides high performance. |
| Scenario | Performance-centric business scenarios. | Business scenarios where hot data and cold data are separately stored, and you are more concerned about how to reduce costs. | This applies to small-sized applications, medium-sized applications, and applications for verification. It also applies to standard Redis usage and data migration scenarios. |
Features
In the following table, ✔️ indicates that this feature is supported, and ❌ indicates that this feature is not supported.
| Category | Item | ApsaraDB for Redis Enhanced Edition (Tair) | ApsaraDB for Redis Community Edition | ||
|---|---|---|---|---|---|
| Performance-enhanced instances | Hybrid-storage instances | Redis 2.8, Redis 4.0, and Redis 5.0 | Redis 6.0 | ||
| Basic performance | Performance benchmark based on Community Edition | 300% | 90%-40% ② | Same | 120% |
| Maximum number of connections to each data node. | 30,000 | 10,000 | 10,000 | 10,000 | |
| Service capability of an individual key (QPS reference value) ① | 450,000 | 120,000-60,000 ② | 140,000 | 160,000 | |
| Specifications | Disk type | Local disk | Local disk | Local disk | Enhanced SSDs (PL1) |
| Enhanced SSDs (PL1) | |||||
| Thread model | Multiple I/O + single Worker (Real Multi-I/O) ③ | Single I/O + multiple Workers | Single I/O + single Worker | Multiple I/O + single Worker | |
| Cost per unit (based on Community Edition) | 117% | 30% | Same | Same | |
| Data structure | Basic data structures and supported commands | Different instances support different commands. For more information, see Limits on commands supported by Enhanced Edition. | For more information about the commands that are not supported, see Commands supported by Community Edition. | ||
| Performance-enhanced instances | ✔️ | ❌ | ❌ | ❌ | |
| Data persistence | Master-replica replication consistency | Eventual consistency | Eventual consistency | Eventual consistency | Eventual consistency |
| Persisted data consistency ④ | Write Back | Write Back | Write Back | Write Back | |
| Persistence level | Within seconds | Within seconds | Within seconds | Within seconds | |
| Security | Audit log feature for databases | ✔️ | ✔️ | ✔️ (not supported in Redis 2.8) | ✔️ |
| SSL encryption | ✔️ | ✔️ | ✔️ | ❌ | |
| IP address whitelist | ✔️ | ✔️ | ✔️ | ✔️ | |
| Advanced features | Data flashback | ✔️ | ❌ | ❌ | ❌ |
| One-way data synchronization by using DTS | ✔️ | ✔️ | ✔️ | ✔️ | |
| Two-way data synchronization by using DTS | ✔️ | ❌ | ❌ | ❌ | |
The following sections show the description of each number label:
- ①: The QPS (number of visits per second) reference value is measured by a command with time complexity of O(1). A higher time complexity indicates a lower QPS reference value.
- ②: A higher hit ratio on memory indicates that hybrid-storage instances provide higher performance. The performance is similar to that of Community Edition.
- ③ Different from the multi-threading feature of Redis Community Edition 6.0, Real Multi-I/O of performance-enhanced instances supports multiple connections, linear increases in throughput, and provides fully accelerated I/O threads.
- ② ApsaraDB for Redis uses the following methods to store data:
- Write Through: writes the data directly to disks and returns a successful response.
- Write Back: writes the data to the cache and returns a successful response. The data will be written to disks later.