Comparing DCS and Open-Source Cache Services
DCS supports single-node, master/standby, and cluster instances, ensuring high read/write performance and fast data access. It also supports various instance management operations to facilitate your O&M. With DCS, you only need to focus on the service logic, without concerning about the deployment, monitoring, scaling, security, and fault recovery issues.
DCS is compatible with open-source Redis, and can be customized based on your requirements. This renders DCS unique features in addition to the advantages of open-source cache databases.
DCS for Redis vs. Open-Source Redis
| Feature | Open-Source Redis | DCS for Redis |
|---|---|---|
| Service deployment | Requires 0.5 to 2 days to prepare servers. |
|
| Version | - | Deeply engaged in the open-source community and supports the latest Redis version. Currently, Redis 4.0, 5.0, 6.0, and 7.0 are supported. |
| Security | Network and server safety is the user's responsibility. |
|
| Performance | - | x86-based: 100,000 QPS per shard. QPS per shard for a Redis 6.0 enterprise (performance) instance node: 400,000/s; QPS per shard for an enterprise (storage) instance node: 70,000/s. |
| Monitoring | Provides only basic statistics. | Provides more than 30 monitoring metrics and customizable alarm threshold and policies.
|
| Backup and restoration | Supported |
|
| Parameter management | No visualized parameter management |
|
| Scale-up | Interrupts services and involves a complex procedure, from modifying the server RAM to modifying Redis memory and restarting the OS and services. |
|
| O&M | Manual O&M | 24/7 end-to-end O&M services |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.