Combining RDB and AOF
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, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access