This article explains why Redis data must be persisted, compares the two built‑in methods—RDB snapshotting and Append‑Only File (AOF)—and provides practical configuration tips, command usage, performance considerations, and verification tools for reliable backup and recovery.
Redis is an open-source, in‑memory data structure store offering high‑performance caching, persistence, replication, and rich data types such as strings, lists, sets, hashes, and sorted sets, and this guide compares its strengths and differences with Memcached and other databases.
This article explains Redis fundamentals, its key‑value storage model, advanced data structures, persistence mechanisms (RDB and AOF), replication architecture, and how Sentinel provides automated failover and high‑availability management, complemented by practical configuration examples and performance considerations.
The article dissects Redis’s architecture by examining its single‑threaded reactor network model, core data structures and memory‑management tactics, AOF/RDB persistence mechanisms, and master‑slave, Sentinel, and Cluster multi‑node strategies, highlighting how each design choice balances speed, memory usage, and system complexity.
The article evaluates storage options for shared collections across multiple machines, explains why Redis 3.2 meets high‑availability, persistence, and data‑structure needs, and details the chosen deployment using master‑slave replication, Sentinel clusters, and supporting scripts.
This article provides a detailed comparison of Memcached and Redis by examining their service models, event loops, memory allocation strategies, database structures, persistence mechanisms (RDB and AOF), transaction support, and publish‑subscribe features, highlighting the design choices, trade‑offs, and implementation nuances of each key‑value caching system.
This article explains Redis's five primary data types—String, Hash, List, Set, and Sorted Set—detailing their commands, use‑cases, internal encodings, memory‑saving configuration parameters, and the available persistence strategies, while offering practical recommendations for production deployments.
This article compares Redis and Memcached across data‑type support, memory‑usage efficiency, performance, memory‑management mechanisms, persistence options, and clustering capabilities, highlighting the strengths and trade‑offs of each in‑memory data store.
This article examines the various scenarios that cause Redis to block—such as expensive commands, fork‑induced overhead, and persistence operations—and provides practical architectural and configuration solutions to keep the event loop responsive even with large data volumes.
This article demonstrates how to use Python to copy a malicious executable to the %TEMP% directory, modify the Windows registry Run key for persistence, and establish a Base64‑encoded reverse shell that connects back to a hard‑coded attacker IP, illustrating common Windows malware techniques.
This article critically examines common claims that Memcached is superior for caching by comparing its design, threading, disk I/O, memory efficiency, LRU behavior, smart caching features, persistence, replication, observability, and Lua scripting capabilities against Redis, concluding that the two systems have distinct trade‑offs depending on use case.
Redis’s AOF persistence logs every write command, causing the log file to grow, but the AOF rewrite feature creates a compact new file by replaying the current dataset, runs in a child process, and uses a buffer to avoid blocking and ensure data consistency.
Redis offers two persistence strategies—RDB snapshots and AOF command logging—each with distinct generation methods, configuration options, and recovery processes, allowing users to balance speed, safety, and data durability based on workload requirements.