This topic compares the features of ApsaraDB for Redis Enhanced Edition (Tair) and Community Edition to help you select an instance series that meets your business requirements.

Key features and supported scenarios

ApsaraDB for Redis Enhanced Edition (Tair)DRAM-based instancesPerformance-centric business scenarios.
Persistent memory-optimized instances
  • Persistent memory-optimized instances provide ultra-high cost-effectiveness. The price of persistent memory-optimized instances is 30% lower than that of ApsaraDB for Redis Community Edition instances with the same capacity. The performance of persistent memory-optimized instances reaches 90% of that of native Redis databases.
  • Persistent memory-optimized instances support the TairString (including CAS and CAD commands), TairHash, and TairCpc enhanced data structure modules.
  • Persistent memory-optimized instances prevent data loss when power failures occur. These instances implement persistence for each command. The system will return a success response for each write operation only after the data is persistently stored. You can use persistent memory-optimized instances as in-memory databases instead of caches.
  • Persistent memory-optimized instances optimize the append-only file (AOF) rewriting performance for large-sized Redis databases. These instances reduce the latency and jitters that are caused when Redis calls forks to rewrite the AOF.
  • Persistent memory-optimized instances deliver high compatibility. These instances are compatible with most data structures and commands of native Redis databases.
Data cache and storage scenarios that require high performance and high data persistence, and can bear high costs.
ESSD-based instances
  • Reduces costs. These instances reduce up to 85% of costs compared with ApsaraDB for Redis Community Edition instances.
  • Stores data in cloud disks. These instances store data in ESSDs to ensure high data reliability. The capacity of an ESSD-based instance reaches hundreds of terabytes. For more information, see ESSDs.
  • Optimizes memory usage for large Redis databases. These instances reduce the amount of memory that is reserved for the forks of native Redis databases.
  • Delivers high compatibility. ESSD-based instances are compatible with most data structures and commands of native Redis databases.
Data storage scenarios that require a large capacity and low costs, involve only infrequent data access, and may cause high access latency.
ApsaraDB for Redis Community EditionN/ACompatible 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.
Note For more information about instance series, see Select an ApsaraDB for Redis instance.

Feature comparison

In the following table, ✔️ indicates that this feature is supported, and ❌ indicates that this feature is not supported.

Note Hybrid-storage instances are phrased out. For more information, see End-of-Sale for ApsaraDB for Redis hybrid-storage instances. We recommend that you choose Persistent memory-optimized instances.

If you have purchased a hybrid-storage instance, you can submit a ticket to migrate the data of the instance.

CategoryFeatureApsaraDB for Redis Enhanced Edition (Tair)ApsaraDB for Redis Community Edition
DRAM-based instancesPersistent memory-optimized instancesESSD-based instancesHybrid-storage instances (phased out)Instances that runs Redis 2.8, 4.0, or 5.0Instances that runs Redis 6.0
Basic performancePerformance benchmark (based on Community Edition)300%90%Read: 50%90% to 40% ②Same120%
Write: 30%
Maximum number of connections to each data node30,00010,00010,00010,00010,00010,000
Service capability of a single key (QPS reference value) ①450,000130,00060,000 to 30,000 ②120,000 to 60,000 ②140,000160,000
Maximum bandwidth (Mbit/s)96~204896~2048128~102448~153610~204810~2048
SpecificationsDisk typeLocal disksPersistent memoryPL1 ESSDsLocal disksLocal disksPL1 ESSDs
Threading modelMultiple I/O threads + single worker thread (the Real Multi-I/O model) ③Single I/O thread + single worker threadMultiple I/O + multiple workers (Real Multi-I/O) Single I/O thread + multiple worker threadsSingle I/O thread + single worker threadMultiple I/O + single worker
Cost per unit (based on Community Edition)117%70%15%~20%30%SameSame
Data structuresBasic data structures and supported commandsDifferent 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 not supported, see Commands supported by ApsaraDB for Redis Community Edition.
Integration of multiple Redis modules✔️✔️️️️️ (integration with specific Redis modules)
Data persistenceMaster-replica replication consistencyEventual consistencyEventual consistencyEventual consistencyEventual consistencyEventual consistencyEventual consistency
Persistent data consistency ④Write BackWrite ThroughWrite ThroughWrite Back Write BackWrite Back
Persistence levelWithin secondsCommand-levelCommand-levelWithin secondsWithin secondsWithin seconds
Data securityAudit logs✔️✔️
SSL encryption✔️✔️✔️
Performance analysisUse the real-time key statistics feature✔️✔️✔️✔️✔️
Query historical hotkeys✔️✔️
Real-time large key query✔️✔️✔️ (not supported in Redis 2.8)✔️
Offline large key analysis✔️✔️✔️✔️✔️
Advanced featuresUse data flashback to restore data by point in time✔️
Proxy query cache✔️
Global Distributed Cache✔️
One-way data synchronization by using Data Transmission Service (DTS)✔️ ✔️✔️✔️
Two-way data synchronization by using DTS✔️✔️✔️
The following section provides the description of each numeric label:
  • ①: The queries per second (QPS) reference value is measured by a command with a time complexity of O(1). The higher the time complexity, the lower the 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 the instance provides the performance closer to that of a Community Edition instance.
  • ③: Different from the multi-threading model of Community Edition 6.0, the Real Multi-I/O model of DRAM-based instances provides fully accelerated I/O threads to support connections and linearly increases throughput.
  • ④: Tair 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, returns a success response, and then writes the data to disks.