Consider Lettuce instead of Jedis as default Redis driver dependency
See original GitHub issueLettuce is the preferred Redis driver for Spring Data Redis and Spring Session supporting the most recent Redis versions. We should consider whether to replace Jedis with the Lettuce driver in spring-boot-starter-data-redis
. There are a couple of aspects that play into this request:
- Lettuce comes with a friendlier performance profile than Jedis.
- The arrangement with Jedis suffers from changes in the Jedis core development. Features of newer Redis versions are not supported.
- Requests for a new release were not completed in a timely manner.
On the other side, Lettuce 5 requires Java 8, netty 4.1 and Project Reactor 3.1. It no longer requires Google Guava.
Related issues:
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Jedis vs. Lettuce: An Exploration | Redis
Lettuce is a Redis Java client that is fully non-blocking. It supports both synchronous and asynchronous communication. Its complex abstractions ...
Read more >Spring Auto Configuration prioritization between Lettuce or Jedis
I want to use Lettuce as a Redis Client, which is the default dependency for spring-boot-starter-data-redis-reactive.
Read more >Introduction to Lettuce - the Java Redis Client - Baeldung
Similar to Jedis, Lettuce provides a complete Redis command set in the form of methods. However, Lettuce implements both synchronous and ...
Read more >Lettuce Reference Guide
Lettuce is a scalable thread-safe Redis client based on netty and Reactor. Lettuce provides synchronous, asynchronous and reactive APIs to ...
Read more >Spring Data Redis
With that in place, you can declare the Spring Data modules you would ... or above and Spring Data Redis integrates with Lettuce...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m now in favour of making this switch in 2.0.
The dep is mandatory so nothing is really lost. I wonder about the naming inconsistency now. Let’s reopen and see what the rest of the team thinks.