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

Edition Series Feature Scenario
ApsaraDB for Redis Enhanced Edition (Tair) Performance-enhanced instances
  • Performance-enhanced instances use the multi-threading model and provide read and write performance approximately three times that of ApsaraDB for Redis Community Edition instances with the same specifications.
  • Performance-enhanced instances provide multiple enhanced data structure modules such as TairString (including CAS and CAD commands), TairHash, TairGIS, TairBloom, TairDoc, TairTS, TairCpc, TairZset, TairRoaring, and TairSearch. These instances eliminate concerns about storage structure and timeliness and allow you to focus on business development.
  • Performance-enhanced instances provide high compatibility. Performance-enhanced instances are fully compatible with open source Redis. You can switch from open source Redis to ApsaraDB for Redis without the need to modify application code.
  • Performance-enhanced instances provide a variety of enterprise-grade features such as data flashback, proxy query cache, and Global Distributed Cache for Redis. For more information, see Use data flashback to restore data by point in time, Use proxy query cache to address issues caused by hotkeys, and Overview.
Performance-centric business scenarios.
Persistent memory-optimized instances
  • Provides 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) and TairCpc enhanced data structure modules.
  • Prevents data loss when power failures occur. Persistent memory-optimized instances implement data persistence for each command. The system returns 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.
  • Optimizes append-only file (AOF) rewriting performance for large-sized Redis databases. Persistent memory-optimized instances reduce the latency and jitters that are caused when Redis calls forks to rewrite the AOF.
  • Delivers high compatibility. Persistent memory-optimized 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.
Storage-optimized instances
  • Storage-optimized instances reduce costs. These instances reduce up to 85% of costs compared with ApsaraDB for Redis Community Edition instances.
  • Storage-optimized instances store data in disks. These instances store data in enhanced SSDs (ESSDs) with high data reliability. The capacity of a storage-optimized instance reaches hundreds of terabytes. For more information about ESSDs, see ESSDs.
  • Storage-optimized instances optimize memory usage for large-sized Redis databases. These instances reduce the amount of reserved memory that is required for the forks of native Redis databases.
  • Storage-optimized instances deliver high compatibility. Storage-optimized 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 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.
Note For more information about instance types, see Select ApsaraDB for Redis instances.

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 discontinued. For more information, see Sales of ApsaraDB for Redis hybrid-storage instances are discontinued. We recommend that you use performance-enhanced instances that provide higher performance and more features.

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
ESSDs (PL1)
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 ✔️
Overview ✔️
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.