intermediate~2h
Redis — The Java Client Ecosystem: Lettuce, Jedis & Redisson
Every code example so far in this category has used one client without naming it. This chapter names the three real options a Spring Boot project actually chooses between — Lettuce, Jedis, and Redisson — and what each one's design actually buys or costs you, so picking one stops being a coin flip.
Learning objectives
- Explain the thread-safety model of Jedis's connection pool versus Lettuce's single shared connection.
- Describe why Lettuce's async/reactive design is built on Netty and what that buys under concurrent load.
- List what Redisson adds on top of raw command execution — its distributed-objects layer.
- Identify which client Spring Boot's spring-boot-starter-data-redis uses by default, and why.
- Choose the right client for a given Spring Boot project's concurrency and feature needs.
This is a Pro chapter
Sign in, then upgrade to Pro or Power to unlock this and the full Databases Mastery library.
Redis — The Java Client Ecosystem: Lettuce, Jedis & Redisson