Redis: Weekly Recap - Replication, Persistence, and Memory Efficiency

This week centered on three heavyweight features reaching merge or open-review status: replication stream compression, a new backup-and-restore system built on multi-part AOF, and a memory-saving hash template encoding. Alongside those, several correctness fixes landed for ACL key checks, AOF rewrites, and I/O thread stability.

Duration: PT3M14S

Episode overview

This episode is a short developer briefing from Redis.

It explains recent repository work in plain language.

  • Show: Redis
  • Published: 2026-07-20T09:28:35Z
  • Audio duration: PT3M14S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Redis developer briefing for the week of July 13 to July 20, 2026. Thirty-seven pull request activity items and 21 additional commits this week.

The clearest pattern: big infrastructure investments are landing back to back. Replication, persistence, and data encoding all got major upgrades, and the team is already following up with fixes and doc corrections for each.

Start with replication. PR 15366 introduces zstd compression for the replication stream, available when I-O threads are enabled. That builds directly on the I-O thread work from a few weeks prior, and it came with a fast follow, PR 15490, correcting the sample config and readme so operators know compression ships…

Second theme: persistence is expanding in scope. PR 15441 adds a full backup and restore system reusing multi-part AOF, letting cluster deployments stagger snapshot creation across nodes instead of forcing every node to fork at once. That sits alongside two AOF correctness fixes: PR 15466 stops duplicate…

Third theme: memory efficiency at the data-structure level. PR 15364 introduces hinted hash templates, letting many hashes that share the same field names store those names once instead of per key, with a new…

S…

Nearby episodes from Redis

  1. Replication Compression Lands, Durability Bugs Squashed
  2. Build Environment Cleanup
  3. Storage Overhauls and a Security Patch
  4. Correctness Fixes and a Module Refresh
  5. Correctness Under Concurrency
  6. Cleaning Up the Core Before 8.10
  7. Replication Under Load Gets a Fix
  8. Edge Cases in Numeric Boundaries