comparison between ApsaraDB for Redis Enhanced Edition (Tair) and ApsaraDB for Redis Community Edition - ApsaraDB for Redis

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

Main features and supported scenarios

Edition	Series type	Feature	Scenario
Enhanced Edition (Tair)	DRAM-based instances	Provides ultra-high performance. These instances use the multi-threading model to provide read and write performance three times that of native Redis databases or ApsaraDB for Redis Community Edition instances of the same specifications. For more information, see Performance whitepaper of Redis 5.0-compatible Tair DRAM-based instances and Performance whitepaper of Redis 6.0-compatible Tair DRAM-based instances. Provides a variety of self-developed enhanced data modules. These modules include exString (including commands that enhance Redis string functionality), exHash, GIS, Bloom, Doc, TS, Cpc, exZset, Roaring, Vector, and Search. With these modules, you can spend less time writing code, improve business performance, and focus on innovation. Provides enterprise-class features, such as data flashback based on point-in-time recovery (PITR), proxy query cache, and Global Distributed Cache for Tair. Supports enterprise-class encryption methods, such as Transport Layer Security (TLS) encryption and transparent data encryption (TDE). For more information, see Enable TLS encryption and Enable TDE.	Performance-centric business scenarios
	Persistent memory-optimized instances	Offers 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. For more information, see Performance white paper of persistent memory-optimized instances. Supports enhanced data modules. These modules include exString (including commands that enhance Redis string functionality), exHash, and Cpc. Prevents data loss caused by power failure. These instances implement persistence for each command. The system returns 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.	Data caching 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. For more information, see Performance white paper of ESSD-based 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. Optimizes memory usage for large Redis databases. These instances reduce the amount of memory that is reserved for the forks of native Redis databases. Offers high compatibility. These instances are compatible with most data structures and commands of open source Redis.	Data storage scenarios that require a large capacity and low costs, involve only infrequent data access, and can bear high access latency
Community Edition	N/A	Community Edition instances are compatible with open source Redis and provide high performance.	Standard Redis usage and data migration scenarios

Note

For more information about instance selection, see Instructions for selecting an appropriate ApsaraDB for Redis instance.

Feature comparison

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

Category	Item	Enhanced Edition (Tair)			Community Edition
Category	Item	DRAM-based instance	Persistent memory-optimized instance	ESSD-based instance	Instance that runs Redis 2.8, 4.0, or 5.0	Instance that runs Redis 6.0 or 7.0	Cost-efficient instance that runs Redis 5.0 or 6.0
Baseline performance	Performance benchmark (based on Community Edition)	300%	90%	Read: 50%	Same	120%	120%
	Performance benchmark (based on Community Edition)	300%	90%	Write: 30%	Same	120%	120%
	Maximum number of connections to each data node	30,000	10,000	10,000	10,000	10,000	10,000
	Service capability of a single key (QPS reference value] ①	450,000	130,000	30,000~60,000	140,000	160,000	160,000
	Maximum bandwidth (MB/s)	96~2048	96~2048	128~1024	10~2048	48~2048	96~2048
Specifications	I/O and worker models	Multiple I/O threads + Single worker thread (Real Multi-I/O) ③	Single I/O thread + Single worker thread	Multiple I/O threads + Multiple worker threads (Real Multi-I/O)	Single I/O thread + Single worker thread	Multiple I/O threads + Single worker thread	Multiple I/O threads + Single worker thread
Specifications	Cost per unit (based on Community Edition)	117%	70%	15%~20%	Same	Same	51~67%
Data structures	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 not supported, see Commands supported by ApsaraDB for Redis Community Edition.
Data structures	Extended data structures of Tair	✔️	️ ️️️✔️️️ (integration with specific Redis modules)	❌	❌	❌	❌
Data persistence	Master-replica replication consistency	Eventual consistency	Eventual consistency	Eventual consistency	Eventual consistency	Eventual consistency	Eventual consistency
	Persistent data consistency ④	Write Back	Write Through	Write Through	Write Back	Write Back	Write Back
	Persistence level	Within seconds	Command-level	Command-level	Within seconds	Within seconds	Within seconds
Security	Audit logs	✔️	✔️	❌	✔️	✔️	✔️
	TLS encryption	✔️	✔️	❌	✔️	✔️	✔️
	TDE	✔️	❌	❌	❌	❌	❌
	Whitelists	✔️	✔️	✔️	✔️	✔️	✔️
Performance analysis	Real-time key statistics	✔️	✔️	✔️	✔️	✔️	✔️
	Query of historical hotkeys	✔️	✔️	❌	✔️	✔️	✔️
	Offline large key analysis	✔️	✔️	❌	✔️	✔️	✔️
Advanced features	Data flashback for data restoration by point in time	✔️	✔️	❌	❌	❌	❌
	Proxy query cache	✔️	❌	❌	❌	❌	❌
	Global Distributed Cache	✔️	❌	❌	❌	❌	❌
	One-way data synchronization by using DTS	✔️	✔️	❌	✔️	✔️	✔️
	Two-way data synchronization by using DTS	✔️	✔️	✔️	❌	❌	❌

The following points illustrate 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.