Redis does not instantly release memory for expired keys; instead it employs three deletion strategies—timed, periodic, and lazy—to balance memory usage, CPU load, and data accuracy, with periodic scans optimized by random sampling and time limits.
Redis uses both time‑based and lazy expiration, marking keys as expired at their TTL but only removing them on the next access or during periodic cleanup, so expired keys are not deleted the instant they expire.
This article explains how to use Redis key expiration notifications combined with a strategy pattern to create real‑time overdue reminders for workflow tasks, covering configuration, listener implementation, distributed locking, message handling, and practical usage in a SpringBoot project.
This article examines the pitfalls of using Redis key‑expiration notifications for delayed business actions, presents a Docker‑based benchmark, provides Spring‑Boot code for scheduling and listening to expirations, and analyzes how notification latency grows as the number of keys increases.
This article explains Redis databases, the structure of the keyspace, how to set key expiration, and the various memory reclamation and eviction policies, providing Java developers with the essential knowledge needed for advanced Redis interview questions.
Redis uses key expiration commands, periodic scanning, and a combination of lazy and active deletion strategies, and when memory is full it applies one of eight eviction policies—including refined LRU and LFU algorithms with sampling and decay mechanisms—to decide which keys to discard.
This article explains how to use Redis key‑expiration events in a Spring Boot application to automatically close unpaid orders by configuring Redis, adding the necessary dependencies, and implementing a listener that reacts to expired keys.
This article demonstrates how to use Redis key‑expiration notifications together with Spring Boot to automatically close orders that remain unpaid after a configurable timeout, eliminating inefficient polling and providing a clean backend solution for order lifecycle management.
This guide explains how to use Redis key expiration notifications in a Spring Boot application to automatically close unpaid orders by storing an order‑ID key with a TTL, configuring Redis to emit expiration events, and implementing a listener that updates order status when the key expires.
This guide walks through diagnosing GPG signing failures caused by expired keys during a swagger‑spring‑boot‑starter release, shows how to inspect the current keyring, edit the key, extend its validity, and finally re‑run Maven deploy to publish artifacts.
This article provides a comprehensive, source‑code‑driven walkthrough of the Redis client‑server interaction, detailing the six main steps from socket establishment to command execution and response, while also covering auxiliary mechanisms such as beforeSleep processing, key expiration strategies, and the underlying epoll I/O multiplexing model.
Redis uses both lazy and periodic deletion strategies to remove expired keys, balancing CPU usage and memory efficiency, and these strategies also affect how persistence mechanisms like RDB and AOF as well as master‑slave replication handle expired keys.
