What’s New in Redis 6.0? Key Features and Improvements Explained
Redis 6.0.0 stable release brings major updates such as redesigned client‑side caching, immediate RDB deletion for replication, enhanced ACL logging, faster PSYNC2 partial resynchronization, decimal timeout support, up to 30% faster RDB loading, and a new STRALGO command for string algorithms.
Redis author announced the stable release of Redis 6.0.0.
From RC1 to now, several changes have been made:
Client‑side caching has been redesigned, dropping the caching slot and using only key names.
Redis now supports a mode where an RDB file used for replication is deleted immediately when it becomes obsolete, allowing pure in‑memory operation.
ACL improvements include a new ACL LOG command that records every ACL violation, showing the client, the disallowed command, and the key, which helps debugging.
The replication protocol PSYNC2 has been enhanced, enabling more frequent partial resynchronizations and allowing replicas to find a common offset with the master.
Commands with timeouts now accept decimal values, extending support beyond whole‑second BLPOP.
RDB loading is 20‑30 % faster depending on file composition, and information is delivered more quickly when many clients are connected.
A new STRALGO command implements complex string algorithms; currently it provides LCS (longest common subsequence), useful for comparing viral RNA or DNA sequences.
Redis 6 is the largest release to date; although it is stable, it should be tested with production workloads before deployment, and a Redis 6.0.1 patch is planned.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Programmer DD
A tinkering programmer and author of "Spring Cloud Microservices in Action"
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
