Comparison between Tair (Enterprise Edition) and Redis Open-Source Edition - Tair (Redis® OSS-Compatible)

This topic compares the features of Tair (Enterprise Edition) and Redis Open-Source Edition to help you choose an instance type that meets your business requirements.

Features and scenarios of each series type

Edition	Series type	Feature	Scenario
Tair (Enterprise Edition)	DRAM-based instances	Provides ultra-high performance. DRAM-based instances use the multi-threading model to provide read and write performance three times that of Redis Open-Source Edition instances that have 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, exZset, GIS, Bloom, Doc, TS, Cpc, Roaring, Search, and Vector. These modules allow you to spend less time writing code, improve business performance, and focus on innovation. Provides enterprise-class features, such as point-in-time data restoration by using data flashback, proxy query cache, and Global Distributed Cache. 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 approximately 30% lower than that of Redis Open-Source Edition instances that have the same capacity. The performance of persistent memory-optimized instances reaches 90% of that of Redis Open-Source Edition instances. For more information, see Performance whitepaper 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. Persistent memory-optimized 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/SSD-based instance	Reduced costs: ESSD/SSD-based instances reduce up to 85% of costs compared with Redis Open-Source Edition instances. High performance: An ESSD/SSD-based instance delivers approximately 60% of the performance of a Redis Open-Source Edition instance. For more information, see Performance whitepaper of ESSD-based instances. Storage in disks: ESSD/SSD-based instances store data in ESSDs or SSDs to ensure high data reliability. The capacity of an ESSD/SSD-based instance can reach hundreds of terabytes. Data distribution: ESSD/SSD-based instances use the Alibaba Cloud TairDB storage engine and combine disks and memory to provide an optimal balance between data persistence and quick access to data. High compatibility: ESSD/SSD-based instances are compatible with most data structures and commands of Redis 6.0.	Data storage scenarios that require a large capacity and low costs, involve only infrequent data access, and can bear high access latency
Redis Open-Source Edition	N/A	Redis Open-Source 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 Tair (Redis OSS-compatible) instance.

Feature comparison

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

Category	Item	Tair (Enterprise Edition)				Redis Open-Source Edition
Category	Item	DRAM-based instance	Persistent memory-optimized instance	ESSD-based instance	SSD-based instance	2.8, 4.0, or 5.0 instance	6.0 or 7.0 instance	Cost-effective 5.0 or 6.0 instance
Baseline performance	Performance benchmark (based on Redis Open-Source Edition)	300%	90%	Read: 40%	Read: 60%	Same	120%	120%
	Performance benchmark (based on Redis Open-Source Edition)	300%	90%	Write: 30%	Write: 40%	Same	120%	120%
	Maximum number of connections to each data node	30,000	10,000	10,000	40,000	10,000	10,000	10,000
	Service capability of a single key (QPS reference value) ①	450,000	130,000	30,000~60,000	50,000~60,000	140,000	160,000	160,000
	Maximum bandwidth (Mbit/s)	96~2,048	96~2,048	187.5~1,000	187.5~2,048	10~2048	48~2,048	96~2,048
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)	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 Redis Open-Source Edition)	117%	70%	15%~20%	15%	Same	Same	51~67%
Data structure	Basic data structures and supported commands	Different types of instances support different commands. For more information, see Limits on commands supported by Tair (Enterprise Edition).				For more information about the commands that are not supported, see Commands supported by Redis Open-Source Edition.
Data structure	Extended data structures	✔️	️️️️️️️✔️ ️️️️️️(integration with specific Redis modules)	❌	❌	❌	❌	❌
Data persistence	Master-replica replication consistency	Eventual consistency	Eventual consistency	Eventual consistency	Eventual consistency	Eventual consistency	Eventual consistency	Eventual consistency
	Persistent data consistency ④	Write Back	Write Through	Write Through	Write Through	Write Back	Write Back	Write Back
	Persistence-level	Within seconds	Command-level	Command-level	Command-level	Within seconds	Within seconds	Within seconds
Security	Audit logs	✔️	✔️	✔️	✔️	✔️	✔️	✔️
	TLS encryption	✔️	✔️	❌	❌	✔️	✔️	✔️
	Transparent Data 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	✔️	✔️	❌	❌	❌	❌	❌
	Use proxy query cache to address issues caused by hotkeys	✔️	❌	❌	❌	❌	❌	❌
	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 performance closer to that of Redis Open-Source Edition.
③: Different from the multi-threading model of Redis 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.