This topic compares the features of ApsaraDB for Redis Enhanced Edition (Tair) and the Community Edition.
Key features and applicable scenarios
|Type||ApsaraDB for Redis Enhanced Edition (Tair)||ApsaraDB for Redis Community Edition|
|Performance-enhanced instances||Hybrid-storage instances|
|Key features||Provides high performance and more data structures to simplify development and improve data storage and processing performance.||Reduces costs and ensures the performance for hot data access.||Compatible with open source Redis databases and provides high performance.|
|Scenarios||Scenarios that require high performance for cache and regardless of cost.||The business data is divided into hot data and cold data. In these scenarios, you are more concerned about methods 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.|
In the following table, ✔️ indicates that this feature is supported, and ❌ indicates that the feature is not supported.
|Type||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% to 40% ①||The same||120%|
|Maximum number of connections to each data node.||30,000||10,000||10,000||10,000|
|The service capability of one key (OPS). The commands that have the time complexity of O(1) are used as references.||450,000||120,000 to 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-IO) ②||Single I/O + multiple Worker nodes||Single I/O + multiple Worker nodes||Multiple I/O + single Worker|
|Cost per unit (based on Community Edition)||200%||30%||The same||The 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.|
|AOF persistence||Master-replica replication consistency||Eventual consistency||Eventual consistency||Eventual consistency||Eventual consistency|
|Disk consistency ③||Write Back||Write Back||Write Back||Write Back|
|Persistence level||Within single-digit seconds||Within single-digit seconds||Within single-digit seconds||Within single-digit seconds|
|Security||Audit log feature for databases||✔️||✔️||✔️ (not supported in Redis 2.8)||✔️|
|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:
- ① A higher hit ratio on memory indicates that hybrid-storage instances provide a higher performance. This performance is similar to that of Community Edition.
- ② Different from the multi-threading feature of Redis 6.0, Real Multi-IO of performance-enhanced instances supports multiple connections, linear increases in throughput, and provides fully accelerated I/O.
- ③ 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.