Redisson 4.7, the latest release of the leading Java distributed data grid (IMDG) and coordination framework for the Redis/Valkey ecosystem, has been officially released alongside the newest Redisson PRO architecture. This deep-dive (translated from a zhichai.net analysis) examines the release's architecture and its implications for high-concurrency, cloud-native systems.
Key Points
Redisson 4.7 is built on five pillars:
- New
RMapsbatch operations — pipelined, batch-memory aggregation that removes the network RTT bottleneck when operating on large numbers of distributed Map objects. RCircularBuffer&RRingBuffer— array-based ring memory structures supporting ultra-low-overheadreadNewest()/readOldest()sliding-window reads.- Vector Set — high-dimensional vector storage with Top-K nearest-neighbor (KNN) search, enabling Java developers to build enterprise RAG knowledge bases directly on Redis/Valkey without a dedicated vector database.
- Adaptive Jitter reconnect strategies —
FullJitterDelay/EqualJitterDelayrandomize exponential backoff (Sleep = random(0, min(M, base * 2^attempt))), spreading reconnect requests across the timeline and preventing thundering-herd avalanches when hundreds of thousands of instances reconnect after a failover. - Java 21+ virtual threads and Valkey support — optimized Netty Future async chains coexist with
VirtualThread(M:N scheduling); carrier threads are released when waiting on locks or I/O, supporting hundreds of thousands of concurrent resident tasks. RESP3 auto-negotiation enables deep compatibility with Valkey, Redis 8.0, and low-latency Dragonfly. - Watchdog auto-renewal: when no
leaseTimeis specified, a background task renews the lock every 10 seconds (lease = 30s, renewal at lease/3), eliminating premature lock expiry during long-running business logic. - RedLock: quorum-based acquisition across N independent Redis masters — a lock succeeds only if acquired on at least ⌊N/2⌋ + 1 nodes within the validity window, mitigating lock loss from async master-replica failover.
- RRateLimiter: distributed token-bucket rate limiting with millisecond-level token refill, smoothing flash-sale traffic spikes.
- Full Jitter reconnect: prevents fixed-interval reconnect storms during Redis master-slave failover that would overwhelm the new primary.
- LocalCache with Pub/Sub invalidation: PRO edition two-level caching where data updates broadcast invalidation messages to all nodes, yielding microsecond local reads with cluster-wide eventual consistency.
- Redisson Open-Source 4.7: recommended for standard distributed locks, queues, and rate limiting — covering roughly 95% of distributed coordination scenarios.
- Redisson PRO: recommended for multi-datacenter Active-Active replication and heap-based two-level caching with invalidation sync.
Release matrix (overview)
| Area | Feature | Value |
|---|---|---|
| Distributed collections | RMaps batch ops | Up to ~80% fewer network round-trips |
| Streams | RStream maxCount() / maxSize() | Backpressure protection against consumer OOM |
| Local caching | LocalCache + invalidation broadcast | ~10x read performance, millisecond-level invalidation |
| Runtime | Netty 4.2, Zstandard/LZ4 compression, virtual threads | Reported 3–5x throughput gains |
Distributed Locking and Coordination
Redisson's lock lifecycle management uses Lua scripts for atomicity and provides:
Resilience and Throughput
Enterprise Selection Guidance
References
1. Lamport, L. (1978). *Time, clocks, and the ordering of events in a distributed system*. Communications of the ACM, 21(7), 558-565. DOI: 10.1145/359545.359563
2. Gray, J., & Lamport, L. (2006). *Consensus on transaction commit*. ACM Transactions on Database Systems (TODS), 31(1), 133-160. DOI: 10.1145/1132863.1132867