In the previous recipes of this chapter, we have described both RDB and AOF persistence options. When it comes to data persistence, there are always several factors you should take into consideration: data loss in case of an outage, performance cost when saving data, the size of the persisted file, and the speed of restoring data. For RDB, data written into Redis between two snapshots may get lost. The latency and memory cost of a system call fork()
in RDB may become a problem when the writing traffic is high and the dataset is big. However, compared to AOF, an RDB dumping file takes less disk space, and restoring data from an RDB dump is faster. In fact, you can enable both features at the same time.
In this recipe, we will explore how to take the best of both persistence approaches.
You need to finish the installation of the Redis Server, as we described in the Downloading and installing Redis recipe in Chapter 1, Getting Started with Redis. Basic knowledge...