Redisson is the Java client and real-time data platform for Valkey and Redis, aimed at Java developers who need distributed collections, locks, and services on top of those servers without writing the coordination code themselves.

What it is

Redisson is a thread-safe Java client for Valkey and Redis that goes beyond command execution to supply over 50 Java objects and services implemented on those platforms. It provides distributed versions of the collections and concurrency primitives Java developers already know: Map, Multimap, Set, List, SortedSet, Queue, Deque, Semaphore, Lock, and AtomicLong among them. It supports Redis from 3.0 upward and Valkey from 7.2.5 upward, runs on JDK 1.8 through the latest versions, and is Android compatible. Four API models are exposed: synchronous, asynchronous, RxJava3, and Reactive Streams.

The concrete problem it solves is that Valkey and Redis, as shipped, have no native distributed Java collections or service implementations. A team that wants a distributed lock, a reliable queue, a rate limiter, or a MapReduce service must otherwise hand-roll that logic around raw commands, and get the failure, retry, and reconnection behaviour right. Redisson replaces that hand-rolled coordination layer with ready-made implementations, and it also replaces direct use of a plain Redis client by layering local caching, cache API integrations, and messaging on top of the same connection. It carries an Apache-2.0 licence and sits in the Infrastructure and Operations / Databases category of this registry.

Key capabilities

• Distributed locks and synchronizers: Lock, FairLock, MultiLock, RedLock, ReadWriteLock, Semaphore, PermitExpirableSemaphore, and CountDownLatch.
• Distributed collections and queues: Map, Multimap, Set, List, SortedSet, ScoredSortedSet, LexSortedSet, TimeSeries, VectorSet, BitVector Store, ReliableQueue, Blocking Deque, Priority Queue, Stream, Ring Buffer, and Transfer Queue.
• Cache API implementations for Spring Cache, JCache API (JSR-107), Hibernate Cache, MyBatis Cache, Quarkus Cache, and Micronaut Cache.
• Local cache support, including a Caffeine-based implementation, plus RediSearch and JSON datatype and JSON Store support.
• Probabilistic structures: Bloom filter, Cuckoo filter, HyperLogLog, Top-k, and T-digest; counters include Id generator, AtomicLong, AtomicDouble, LongAdder, and DoubleAdder.
• Services layer covering Remote service, Live Object service, Executor service, Scheduler service, and MapReduce service, with Reliable PubSub, Topic, and Sharded Topic for publish/subscribe.
• Connection handling across Proxy, Multi-Cluster, Multi-Sentinel, Single, Cluster, Sentinel, Replicated, and Master-Slave deployment modes, with auto-reconnection, failed command auto-retry, SSL, OSGi, an asynchronous connection pool, and Lua scripting.

Who uses it and how

• Java teams running Redis or Valkey in Cluster, Sentinel, or Master-Slave mode who need shared locks and collections rather than raw key commands.
• Spring Boot applications, where the Spring Boot Starter and Spring Cache integration replace direct cache wiring.
• Services built on Quarkus, Micronaut, or Helidon, which the microservices integration section targets explicitly.
• Applications already using Hibernate, MyBatis, or JCache (JSR-107) that want the cache backed by Redis or Valkey without changing the caching API.
• Workloads needing schedulers, executors, MapReduce, or reliable queued messaging inside the same client, rather than a separate component.

Getting started

The README points to a Quick start guide at redisson.pro/docs/getting-started/ and full documentation at redisson.pro/docs/, with JavaDocs published for the org.redisson/redisson artifact and runnable samples in the redisson-examples repository. Configuration covers the deployment modes above, so a single node and a cluster are both configured through the same client.

How it compares

The facts provided name no competing Java client or paid product, so this entry stands alone in the registry on that axis. Redisson is best understood as a layer above Valkey and Redis rather than a substitute for them: it depends on those servers, and it adds the distributed collections, locks, and services that neither platform offers natively.

When to use it — and when not to

A self-hoster still has to operate the Valkey or Redis deployment itself, including persistence, failover, and monitoring, because Redisson is a client library and not a managed service. Teams that want a hosted data platform, or that need no distributed locking, queueing, or shared collections, will get little from the added surface area. The repository carries 248 open issues, and the README is a feature catalogue with installation left to the external documentation, so expect to work from the docs site rather than the repository alone.