string, sets, sorted sets, lists, hashes, bitmaps, hyperloglog, geospatial indexes

string, sets, sorted sets, lists, hashes, bitmaps, hyperloglog, geospatial indexes

string, objects (like databases)

Supported

Unsupported

Supported

Only versions 3.2.10 and later 

Yes

Yes

Only versions 3.2.10 and later 

No

No

3.2.6, 4.0.10 and later

3.2.6, 4.0.10 and later

Unsupported

Yes

Yes

Yes

3.2.6, 4.0.10 and later

3.2.6, 4.0.10 and later

No

No

No

Yes

No

Yes

No

Yes

Supported

Supported

Unsupported

Required

Optional

Unsupported

Supported

Supported

Unsupported

Yes

Yes

No

Supported

Supported

Unsupported

Supported

Supported

Unsupported

• You need to partition your data across two to 250 or 500 nodes if the Redis engine version is 5.0.6 or higher.(clustered mode only).

• You need geospatial indexing (clustered mode or non-clustered mode).

• You don’t need to support multiple databases.

• Plus features of non-clustered mode

• You need complex data types, such as strings, hashes, lists, sets, sorted sets, and bitmaps.

• You need to sort or rank in-memory datasets.

• You need persistence of your key store.

• You need to replicate your data from the primary to one or more read replicas for read intensive applications.

• You need automatic failover if your primary node fails.

• You need pub/sub capabilities.

• You need backup and restore capabilities.

• You need to support multiple databases.

• 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, such as a database.

• Needs Auto Discovery to simplify the way an application connects to a cluster.