Tech highlights
Distributions
- Redis
- Operating system provided repository
- Custom repository binaries
Replication types
- Asynchronous replication
Top features
- AUTH enabled security
- Automatic failover
- Resource awareness
Try ClusterControl with Redis for yourself!
Key features list
OSS License | |
Enterprise License | |
Severalnines Support | |
Relational | |
NoSQL | |
Storage Engines | |
Time series | |
Backup & Restore | |
— Full | |
— Incremental | |
— Partial | |
— Restore: PITR | |
— Clone / Duplicate node | |
— Local storage | |
— Cloud storage | |
— Encryption | |
— Compression | |
Cluster creation | |
— Asynchronous Replication | |
— Synchronous Replication | |
— Add node / decommission | |
SSL/TLS Connectivity | |
Load Balancer availability | |
Infrastructure manageability | |
Security | |
— User console access | |
— Key Management | |
— LDAP integration | |
— Audit log | |
Performance analysis | |
— Query monitoring | |
— Operations monitoring | |
— Custom metrics/thresholds | |
— Replication lag | |
Configuration Management | |
Database-specific dashboard | |
Alarms & Error reporting |
I rarely take a backup of my Redis instances, and see you have that option. Can I use it, and how complicated is it?
You can schedule Redis backups or execute on-demand copies from the replica or primary nodes automatically. Store them locally or straight to the cloud, ClusterControl will take care of it all.
We monitor our Redis instances from the CLI. Does ClusterControl offer any option to monitor in addition to deploying?
ClusterControl monitors real-time with customizable intervals commands per second, total keys, connected clients, blocked clients, memory used & replica lag. You can also integrate / execute your own scripts on all nodes via s9s CLI.
With our current Redis instances, we adjust the configuration according to the business activity. How is this done in ClusterControl, if it’s available?
Not only is it available, but you can edit the parameters on all instances from a single window, ensuring all instances have the same config for things like binding to localhost for security reasons.