Redis 7.0: What's New, Release History & EOL Status

What Is New in Redis 7.0

Redis 7.0 delivers significant enhancements across data management, scalability, and operational control. This table summarizes the key areas of improvement.

What new commands should I use in Redis 7.0?

Redis 7.0 introduces several commands that expand data structure operations and server introspection. These additions fill specific gaps in previous versions.

Sorted Set and List Operations

Commands like ZMPOP, ZINTERCARD, and LMOVE provide more flexible ways to manipulate sorted sets and lists. For instance, ZMPOP pops the highest or lowest scoring members atomically, which is useful for task queues.

Library and Function Management

The FUNCTION command family (FUNCTION LOAD, FUNCTION LIST, etc.) allows you to deploy and manage server-side code libraries. This moves beyond simple EVAL scripts to a more maintainable system.

Key Inspection Commands

Use EXPIRETIME and PEXPIRETIME to check the absolute Unix timestamp when a key expires. This is more precise than checking the remaining time with TTL.

How do Redis Functions change server-side scripting?

Redis Functions replace Lua scripts with a managed, library-based approach. You load a function once, and it persists like any other data type, callable by name.

In practice, this means you don't have to transmit the entire script body on every call, reducing network overhead. Functions are also stored in the AOF and replicated to replicas, making them durable and consistent across your data set.

You manage them with the FUNCTION commands. This model is cleaner for production because you version and deploy your logic as a unit, not as inline strings mixed with your application code.

What is Sharded Pub/Sub and when do I need it?

Sharded Pub/Sub scales publish/subscribe messaging across a Redis Cluster. Traditional Pub/Sub broadcasts messages to all nodes, which doesn't work in a clustered environment.

With Sharded Pub/Sub, messages are routed to a specific shard based on the channel name. Clients subscribed to that channel on the correct shard will receive the message. This matters because it lets you build scalable, topic-based messaging systems using Redis Cluster without a separate message broker.

Use it when your Pub/Sub traffic is high and you need the horizontal scalability of a Redis Cluster. The syntax uses SSUBSCRIBE and SPUBLISH for sharded channels.

How does Multi-Part AOF improve persistence?

Multi-part AOF splits the single Append Only File into a sequence of smaller files. A manifest file tracks the order, and Redis can rewrite or truncate these files in the background.

The main benefit is operational. Rewriting a massive single AOF file often caused high disk I/O and latency. Now, the rewrite operates on a base file and incremental files, which is more efficient. Recovery is also more robust because the system can tolerate corruption in a single segment without losing the entire history.

This change is mostly internal. Your configuration and data durability guarantees remain the same, but with better performance during rewrites.

What ACL improvements are most relevant for security?

The Access Control List system now supports key pattern matching. You can define rules that allow or deny commands on keys that match a specific glob-style pattern.

For example, you can create a user that only has read access to keys starting with "cache:" and write access to keys starting with "session:". This granularity was a major missing piece for multi-tenant applications or complex service architectures using a single Redis instance.

ACL rules can also be propagated from a primary to replicas more reliably. In practice, this lets you centralize user management on your primary node and have it automatically apply across your replication topology.