7 hours ago
- RESP3 simplifies client libraries with semantic replies and remains backward compatible with RESP2; attributes for client-side caching may not appear in Redis 6.
- ACLs are primarily for operational safety (e.g., preventing dangerous commands like FLUSHALL) rather than just enterprise security, with low CPU overhead and modular code.
- I/O multi-threading (memcached-style) is unlikely due to complexity; Redis will focus on slow-command threading via module key-level locking and improving Redis Cluster with disk usage orchestration and a proxy.
- Better persistence includes RDB preamble in AOF files and replication improvements in Redis 4 and 5.
- Data structures: Streams added in Redis 5; future work aims at memory efficiency and orthogonal designs rather than many new structures.
- Redis development is opportunistic without a fixed roadmap; blogging helps communicate current priorities and reasons for decisions.