This article has been included in JavaGuide ("Java Learning + Interview Guide" covers the core knowledge that most Java programmers need to master.)
The Redis persistence mechanism belongs to the super-high-frequency interview knowledge points of back-end interviews. It is a cliché, and it takes time to master it. Even if you are not preparing for an interview, daily development needs to be used frequently.
Recently, I took the time to greatly improve the Redis persistence mechanism I wrote before, with both pictures and texts, clear and easy to understand. Share it, I hope it will help you!
Content overview:
When using the cache, we often need to persist the data in the memory, that is, write the data in the memory to the hard disk. Most of the reasons are to reuse data later (such as restarting the machine, recovering data after a machine failure), or for data synchronization (such as the master and slave nodes of the Redis cluster synchronize data through RDB files).
An important point that Redis is different from Memcached is that Redis supports persistence and supports three persistence methods:
- Snapshot (snapshotting, RDB)
- Append only file (append-only file, AOF)
- Hybrid persistence of RDB and AOF (new in Redis 4.0)
Official document address: https://redis.io/topics/persistence .