Mainly depends on whether you use redis as a cache or nosql. If it is a cache, it does not matter if you lose it. Just restore and rebuild from somewhere else. If it is nosql, redis has snapshot and aof mechanisms to ensure data persistence. of
Since it is a cache, my understanding is that it doesn’t matter if it is lost. If it is some user login data, sessionetc., then the user can only be asked to log in again. If it is persisted, you can consider recovering from persistence
It doesn’t matter if the cache is lost but the data has been persisted. In the worst case, you can just rebuild the cache. If it is redis, it can be restored from an aof file. As a cache, it can also be restored using an rdb file. The rdb restore should be faster.
Since it has been persisted, there is nothing to worry about. The redis persistence should be an aof or rdb file. You can just restart and restore it. As for the specific earphone operation, there are detailed articles on the Internet for reference.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Mainly depends on whether you use redis as a cache or nosql. If it is a cache, it does not matter if you lose it. Just restore and rebuild from somewhere else. If it is nosql, redis has snapshot and aof mechanisms to ensure data persistence. of
If it is a cache, then the application logic will not be affected if the cache is lost.
Recover from aof file
Since it is a cache, my understanding is that it doesn’t matter if it is lost.
If it is some user login data,
sessionetc., then the user can only be asked to log in again.If it is persisted, you can consider recovering from persistence
It doesn’t matter if the cache is lost but the data has been persisted. In the worst case, you can just rebuild the cache. If it is redis, it can be restored from an aof file. As a cache, it can also be restored using an rdb file. The rdb restore should be faster.
If it hangs, just restart it. The cache can be hanged. It’s just that the system is under greater pressure.
Since it has been persisted, there is nothing to worry about. The redis persistence should be an aof or rdb file. You can just restart and restore it. As for the specific earphone operation, there are detailed articles on the Internet for reference.
Generally, programs with good design will automatically start the recache logic