This topic compares the features of ApsaraDB for Redis Enhanced Edition (Tair) and Community Edition to help you select an instance type that meets your business requirements.
Key features and supported scenarios
|ApsaraDB for Redis Enhanced Edition (Tair)||Performance-enhanced instances||
||Performance-centric business scenarios.|
|Persistent memory-optimized instances||
||Data cache and storage scenarios that require high performance and high data persistence, and can bear high costs.|
||Data storage scenarios that require a large capacity and low costs, involve only infrequent data access, and can bear high access latency.|
|ApsaraDB for Redis Community Edition||None||ApsaraDB for Redis Community Edition instances are compatible with open source Redis databases and provides high performance.||Small-sized applications, medium-sized applications, applications for verification, and standard Redis usage and data migration scenarios.|
In the following table, ️✔️ indicates that this feature is supported, and ❌ indicates that this feature is not supported.
If you have purchased s hybrid-storage instance, you can submit a ticket to migrate the data of the instance.
|Category||Item||ApsaraDB for Redis Enhanced Edition (Tair)||ApsaraDB for Redis Community Edition|
|Performance-enhanced instances||Hybrid-storage instances (phased out)||Redis 2.8, Redis 4.0, and Redis 5.0|
|Basic performance||Performance benchmark (based on Community Edition)||300%||90% to 40% ②||Same|
|Maximum number of connections to each data node||30,000||10,000||10,000|
|Service capability of a single key (queries per second (QPS) reference value) ①||450,000||120,000 to 60,000 ②||140,000|
|Specifications||Disk type||Local disks||Local disks||Local disks|
|Threading model||Multiple I/O threads+ single worker thread (the Real Multi-I/O model) ③||Single I/O thread + multiple worker threads||Single I/O thread + single worker thread|
|Cost per unit (based on Community Edition)||117%||30%||Same|
|Data structure||Basic data structures and supported commands||Different instances support different commands. For more information, see Limits on commands supported by ApsaraDB for Redis Enhanced Edition (Tair).||For more information about the commands that are supported, see Commands supported by ApsaraDB for Redis Community Edition.|
|Integration with multiple Redis modules||✔️||❌||❌|
|Data persistence||Master-replica replication consistency||Eventual consistency||Eventual consistency||Eventual consistency|
|Persistent data consistency ④||Write Back||Write Back||Write Back|
|Persistence level||Within seconds||Within seconds||Within seconds|
|Security||Enable the new audit log feature||✔️||❌||✔️|
|Configure SSL encryption||✔️||✔️||✔️|
|Step 2: Configure whitelists||✔️||✔️||✔️|
|Performance analysis||Use the real-time key statistics feature||✔️||❌||✔️|
|Query historical hotkeys||✔️||❌||✔️|
|Enable key analysis||✔️||❌||️✔️ (not supported in Redis 2.8)|
|Offline key analysis||✔️||❌||✔️|
|Advanced features||Use data flashback to restore data by point in time||✔️||❌||❌|
|Use proxy query cache to address issues caused by hotkeys||✔️||❌||❌|
|Configure one-way data synchronization between ApsaraDB for Redis instances||✔️||✔️||✔️|
|Configure two-way data synchronization between ApsaraDB for Redis Enhanced Edition (Tair) instances||✔️||❌||❌|
The following sections show the description of each numeric label:
- ①: The QPS reference value is measured by a command with a time complexity of O(1). A higher time complexity indicates a lower QPS reference value.
- ②: This metric is related to the distribution of cold and hot data that is accessed. A higher hit rate on memory indicates that hybrid-storage instances provide higher performance that is closer to that of Community Edition.
- ③: Different from the multi-threading model of Community Edition 6.0, the Real Multi-I/O model of performance-enhanced instances provides fully accelerated I/O threads to support multiple connections and linearly increases throughput.
- ④: ApsaraDB for Redis uses the following methods to store data:
- Write Through: writes data directly to disks and returns a success response.
- Write Back: writes data to the cache and returns a success response, and then writes the data to disks.