A DCS Redis stand-alone instance is deployed according to a single-node architecture without standby nodes for real-time data synchronization, and it can provide data persistence and backup capabilities. It is suitable for cache-only scenarios, such as small-scale applications or development/test environments. It has obvious price advantages and high cost efficiency.
Note:
l Since Redis stand-alone instances adopt a single-node deployment architecture and do not have high availability and service continuity, it is not recommended that you use it in a production environment. But if you do, please be sure to note the risks.
l Redis stand-alone instances can be upgraded to active/standby instances. For details, see Type Changes.
l When a Redis node fails, the system initiates a new Redis process. User data is restored based on the default automatic persistence files to achieve business continuity.
Architecture Diagram
Architecture Description
A stand-alone instance has only one node and one Redis process.
DCS detects instance availability in real time. When it detects that a Redis process has failed, it initiates a new Redis process to restore the business. This operation is completed within seconds.
Application Scenarios
Cache-Only Scenarios
Frequently accessed data can be stored in Redis memory to speed up data reading. Stand-alone instances can meet many small and medium-sized caching needs. If you have high requirements for data availability, it is recommended to use the active/standby instances.
Scenarios with High Redis Protocol Compatibility Requirements
The standard stand-alone instance is fully compatible with the Redis protocol for each business to be smoothly migrated.
Scenarios with Low Performance Pressure
Due to the single-threaded mechanism of Redis, the standard version is not suitable for scenarios with large QPS. If the performance is within 100,000 QPS, the standard version is suitable.