Compared with self-managed Redis databases deployed on your servers, ApsaraDB for Redis instances have multiple benefits, such as high data security, easy O&M, and optimized kernel.
Item | ApsaraDB for Redis | Self-managed Redis |
---|---|---|
Security protection | Beforehand prevention:
|
Beforehand prevention:
|
In-process protection: implements SSL encryption. For more information, see Configure SSL encryption for an ApsaraDB for Redis instance. | In-process protection: requires a third-party tool to implement SSL encryption. | |
Post audit: supports audit logs. For more information, see Query audit logs. | Post audit: does not provide the auditing feature. | |
Backup and restoration | Performance-enhanced instances of ApsaraDB for Redis Enhanced Edition (Tair) support the data flashback feature that allows you to restore data to a specific point in time. For more information about performance-enhanced instances, see Performance-enhanced instances. For more information about the data flashback feature, see Use data flashback to restore data by point in time. | Only full data restoration is supported. |
O&M |
|
|
Deployment and scaling | Supports instant activation and elastic scaling. | Requires a long period of time to complete hardware procurement, hosting of data centers, and machine deployment. You must manage node relationships when you add nodes. |
High availability (HA) |
|
|
Kernel optimization |
|
|
Note ApsaraDB for Redis is fully compatible with native Redis. For more information, see
Which version of Redis is ApsaraDB for Redis compatible with? The way to connect to a database is basically the same for ApsaraDB for Redis and
native Redis. You can choose a client application that is compatible with the Redis
protocol to connect to the database. For more information, see Use a Redis client.