Persistent memory-optimized instances of the ApsaraDB for Redis Enhanced Edition (Tair) adopt Intel Optane DC persistent memory (AEP) to provide large-capacity in-memory databases that are compatible with open source Redis. A persistent memory-optimized instance persists each operation and does not use disks to implement data persistence. Compared with an ApsaraDB for Redis Community Edition instance, a persistent memory-optimized instance reduces costs by up to 30% and delivers almost the same throughput and latency. This improves the reliability of business data.
Instance purchase
Background information
The high price and low capacity of memory limit the large-scale use of memory in specific scenarios. Alibaba Cloud began to invest in the research and implementation of Intel AEP in 2018. Intel AEP was applied to the core cluster of e-commerce products during Double 11 that year and significantly reduced costs. The cluster became a product that officially deployed Intel AEP in a production environment.
Maturer cloud environments and improved AEP-related technologies help Alibaba Cloud develop a new engine for AEP-based data persistence implementation. Alibaba Cloud integrates the new engine with Elastic Compute Service (ECS) bare metal instances to introduce persistent memory-optimized instances of the ApsaraDB for Redis Enhanced Edition (Tair). These instances replace the traditional volatile memory of Redis with persistent memory to significantly reduce the risk of data loss. For more information about ECS bare metal instances, see Overview.
Persistent memory-optimized instances provide not only memory-level access latency and throughput but also data persistence. In addition to reducing costs, persistent memory-optimized instances can simplify the application architecture. The popular architecture that consists of applications, cache, and persistent storage can be simplified to an architecture that consists of applications and persistent memory-optimized instances, as shown in the following figure.
Benefits
Persistent memory-optimized instances of the ApsaraDB for Redis Enhanced Edition (Tair) adopt Intel AEP to provide large-capacity in-memory databases that are compatible with open source Redis. A persistent memory-optimized instance persists each operation and does not rely on disks for data persistence. This helps improve the reliability of business data. Compared with an ApsaraDB for Redis Community Edition instance, a persistent memory-optimized instance reduces costs by up to 30% and delivers almost the same throughput and latency. Persistent memory-optimized instances are suitable for scenarios that store a large amount of hot and warm data, have high requirements for data persistence and service stability, and require compatibility with Redis.
| Item | Description |
|---|---|
| Cost-effectiveness |
|
| Integration with multiple Redis modules |
|
| Optimization for high specifications |
|
| Data loss prevention during power outages |
|
| High compatibility |
|
Scenarios
- Scenarios that require high performance and reduced costs for processing a large amount
of data
Intermediate data computing requires high performance. If you use ApsaraDB for Redis Community Edition for intermediate data computing, the costs are high. Other database types such as HBase cannot meet the performance requirements. Persistent memory-optimized instances not only ensure data persistence but also provide almost the same performance as ApsaraDB for Redis Community Edition instances in terms of throughput and latency. This helps you strike a balance between performance and costs.
- Scenarios that have high requirements for data persistence
For gaming services, persistent memory-optimized instances are used for data storage. Compared with a Redis and MySQL-based architecture, persistent memory-optimized instances provide a simpler architecture, higher performance, higher cost-effectiveness, and higher data reliability.