Check out how ScaleOut In-Memory Database running open-source Redis compares with other implementations of Redis.
Feature
-
ScaleOut In-Memory Database
“One-button scaling; up or down.”
Just connect a server to the cluster. It automatically joins the membership, creates replicas, and rebalances the load. Same for leaving a server.
Other Redis Implementations
Manual Clustering
Clustering requires that you manually create and configure shards on each server and distribute hash slots. This process is complicated, time consuming, and error prone.
-
ScaleOut In-Memory Database
Fewer Servers
Servers host both primary and replica objects within a single service process. This minimizes the number of servers needed.
Other Redis Implementations
More Servers
Redis recommends separate master and replica servers for high availability. That requires more servers for a given data set.
-
ScaleOut In-Memory Database
Robust Self-Healing
After a server or network failure, ScaleOut automatically promotes replica objects to primaries and creates new replicas to “self-heal.” The cluster automatically re-balances the workload. No manual intervention required.
Other Redis Implementations
Manual Restoration
After a failure, Redis promotes replica objects to primaries but does not create new replicas. Recovery requires manual intervention to restore replicas. If both a primary shard and its replica fail, the entire cluster becomes inoperable.
-
ScaleOut In-Memory Database
Full Consistency
Provides full (strong) data consistency with patented technology. Never serves stale data.
Other Redis Implementations
Eventual Consistency
Uses eventual data consistency to update replicas and can serve stale data to applications.
-
ScaleOut In-Memory Database
Uses Multi-Threading
Runs Redis commands using multi- threaded processing to automatically take advantage of all processing cores using one process per server.
Other Redis Implementations
Uses Single-Threading
Redis uses single-threading and runs one command at a time. It requires you to license multiple shards per server to use additional cores.
-
ScaleOut In-Memory Database
Full Linux and Windows Support
Runs natively on Linux or Windows. OSs can be mixed in a single cluster.
Other Redis Implementations
Limited Support
No native Windows support. Runs select versions of Linux.
-
ScaleOut In-Memory Database
“One-button backup and restore.”
Provides fully parallel backup and restore. Allows a different cluster configuration when restoring data.
Other Redis Implementations
Manual Backup and Restore
Users must separately save each node’s database to disk and must restore them to exactly the original cluster configuration.
“One-button scaling; up or down.”
Just connect a server to the cluster. It automatically joins the membership, creates replicas, and rebalances the load. Same for leaving a server.
Manual Clustering
Clustering requires that you manually create and configure shards on each server and distribute hash slots. This process is complicated, time consuming, and error prone.
Fewer Servers
Servers host both primary and replica objects within a single service process. This minimizes the number of servers needed.
More Servers
Redis recommends separate master and replica servers for high availability. That requires more servers for a given data set.
Robust Self-Healing
After a server or network failure, ScaleOut automatically promotes replica objects to primaries and creates new replicas to “self-heal.” The cluster automatically re-balances the workload. No manual intervention required.
Manual Restoration
After a failure, Redis promotes replica objects to primaries but does not create new replicas. Recovery requires manual intervention to restore replicas. If both a primary shard and its replica fail, the entire cluster becomes inoperable.
Full Consistency
Provides full (strong) data consistency with patented technology. Never serves stale data.
Eventual Consistency
Uses eventual data consistency to update replicas and can serve stale data to applications.
Uses Multi-Threading
Runs Redis commands using multi- threaded processing to automatically take advantage of all processing cores using one process per server.
Uses Single-Threading
Redis uses single-threading and runs one command at a time. It requires you to license multiple shards per server to use additional cores.
Full Linux and Windows Support
Runs natively on Linux or Windows. OSs can be mixed in a single cluster.
Limited Support
No native Windows support. Runs select versions of Linux.
“One-button backup and restore.”
Provides fully parallel backup and restore. Allows a different cluster configuration when restoring data.
Manual Backup and Restore
Users must separately save each node’s database to disk and must restore them to exactly the original cluster configuration.
Get to know ScaleOut In-Memory Database with these resources:
Try ScaleOut In-Memory Database for free
Get a 30-day free trial of ScaleOut In-Memory Database (and all of our other products, too).
Get the ScaleOut In-Memory Database product details
Learn more about its automatic cluster management, fully consistent data storage, and automatic sharding.
Read the ScaleOut In-Memory Database announcement blog
Learn how ScaleOut In-Memory Database lowers the total cost of ownership for enterprise Redis developers.