resp3

Bilingual

<antirez>
2 months ago
- Redis 6 introduces client-side caching (tracking) to improve performance by caching data on the client side.
- The feature splits the key space into about 16 million caching slots using a 24-bit CRC64 hash.
- The server maintains an invalidation table mapping slots to client IDs, using ~130MB of memory.
- When a key is modified, the server sends invalidation messages to all clients that have cached data in that slot.
- Clients can enable tracking with CLIENT TRACKING on and optionally redirect invalidation messages to a dedicated connection using REDIRECT.
- RESP3 protocol supports push messages for invalidation; RESP2 can work with redirection and Pub/Sub mode.
<antirez>
2 months ago
- Redis 6 will exclusively use RESP3 protocol, with no server-side RESP2 compatibility mode.
- Mitigations include extended support for Redis 5 (2 years), early unstable release for testing, and optional Lua backward compatibility.
- Reasons for dropping RESP2: avoiding fragmentation, reducing complexity, encouraging migration, and easing client library adaptation.
- RESP3 provides richer semantics (maps, sets, booleans) enabling simpler, more consistent client libraries.
<antirez>
2 months 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.

resp3

<antirez>

<antirez>

<antirez>