Comparing node-based Valkey, Memcached, and Redis OSS clusters
Amazon ElastiCache supports the Valkey, Memcached, and Redis OSS cache engines. Each engine provides some advantages. Use the information in this topic to help you choose the engine and version that best meets your requirements.
Important
After you create a cache, node-based cluster or replication group, you can upgrade to a newer engine version, but you cannot downgrade to an older engine version. If you want to use an older engine version, you must delete the existing cache, node-based cluster or replication group and create it again with the earlier engine version.
On the surface, the engines look similar. Each of them is an in-memory key-value store. However, in practice there are significant differences.
Choose Memcached if the following apply for you:
-
You need the simplest model possible.
-
You need to run large nodes with multiple cores or threads.
-
You need the ability to scale out and in, adding and removing nodes as demand on your system increases and decreases.
-
You need to cache objects.
Choose Valkey or Redis OSS with ElastiCache if the following apply for you:
-
ElastiCache version 9.0 for Valkey
You want built-in full-text search, aggregations, and hybrid search
capabilities that extend the vector search introduced in Valkey 8.2, hash field expiration for per-field TTLs, multi-database support in cluster mode , polygon-based geospatial queries , up to 40% higher throughput with pipelining , or atomic slot migration for safer cluster scaling. For more information, see Valkey 9.0. -
ElastiCache version 8.2 for Valkey
You want native vector search with microsecond latency and 95%+ recall rate. For more information, see Valkey 8.2.
-
ElastiCache version 8.1 for Valkey
You want a new memory-efficient hash table
that reduces memory overhead by up to 20%, native Bloom filter support, the COMMANDLOG command, and up to 514% higher throughput for BITCOUNT. For more information, see Valkey 8.1. -
ElastiCache version 8.0 for Valkey
You want up to 20% better memory efficiency through embedded keys
, per-slot metrics , dual-channel replication , and async I/O threading . For more information, see Valkey 8.0. -
ElastiCache version 7.2 for Valkey or version 7.0 (Enhanced) for Redis OSS
You want to use Functions
, Sharded Pub/Sub , or ACL improvements . For more information, see Redis OSS Version 7.0 (Enhanced). -
ElastiCache version 6.2 (Enhanced) for Redis OSS
You want the ability to tier data between memory and SSD using the r6gd node type. For more information, see Data tiering.
-
ElastiCache version 6.0 (Enhanced) for Redis OSS
You want to authenticate users with role-based access control.
For more information, see Redis OSS Version 6.0 (Enhanced).
| Memcached | Valkey or Redis OSS (cluster mode disabled) | Valkey or Redis OSS (cluster mode enabled) | |
|---|---|---|---|
| Engine versions+ | 1.4.5 and later | 4.0.10 and later | 4.0.10 and later |
| Data types | Simple ‡ | 2.8.x - Complex * | 3.2.x and later - Complex † |
| Complex † | |||
| Data partitioning | Yes | No | Yes |
| Cluster is modifiable | Yes | Yes | 3.2.10 and later - Limited |
| Online resharding | No | No | 3.2.10 and later |
| Encryption | in-transit 1.6.12 and later | 4.0.10 and later | 4.0.10 and later |
| Data tiering | No | 6.2 and later | 6.2 and later |
| Memory efficiencies | No | Valkey 8.0 and later | Valkey 8.0 and later |
| Bloom filters | No | Valkey 8.1 and later | Valkey 8.1 and later |
| Vector search | No | Valkey 8.2 and later | Valkey 8.2 and later |
| Full-text search | No | Valkey 9.0 and later | Valkey 9.0 and later |
| Hybrid search (text + vector) | No | Valkey 9.0 and later | Valkey 9.0 and later |
| Aggregation pipelines | No | Valkey 9.0 and later | Valkey 9.0 and later |
| Hash field expiration | No | Valkey 9.0 and later | Valkey 9.0 and later |
| Numbered databases in cluster mode | No | N/A | Valkey 9.0 and later |
| Compliance certifications | |||
| Compliance Certification
FedRAMP HIPAA PCI DSS |
Yes - 1.6.12 and later Yes - 1.6.12 and later Yes |
4.0.10 and later 4.0.10 and later 4.0.10 and later |
4.0.10 and later 4.0.10 and later 4.0.10 and later |
| Multi-threaded | Yes | No | No |
| Node type upgrade | No | Yes | Yes |
| Engine upgrading | Yes | Yes | Yes |
| High availability (replication) | No | Yes | Yes |
| Automatic failover | No | Optional | Required |
| Pub/Sub capabilities | No | Yes | Yes |
| Sorted sets | No | Yes | Yes |
| Backup and restore | For serverless caches only, not applicable to node-based clusters | Yes | Yes |
| Geospatial indexing | No | 4.0.10 and later | Yes |
| Notes: | |||
| ‡ string, objects (like databases) | |||
| * string, sets, sorted sets, lists, hashes, bitmaps, hyperloglog | |||
| † string, sets, sorted sets, lists, hashes, bitmaps, hyperloglog, geospatial indexes | |||
| + Excludes versions which are deprecated, have reached or soon to reach end of life. | |||
After you choose the engine for your cluster, we recommend that you use the most recent version of that engine. For more information, see Supported node types.
