Jedis lettuce redisson的对比

虎哥和你一起学编程

已于 2023-04-15 05:09:04 修改

阅读量668

点赞数

分类专栏： redis 文章标签： redis

于 2022-01-14 13:18:58 首次发布

本文链接：https://blog.csdn.net/weixin_41751625/article/details/122427480

版权

本文对比了Jedis、Lettuce和Redisson这三种Redis客户端。Jedis为同步阻塞模式，类似JDBC，非线程安全，适合使用连接池。Lettuce采用异步非阻塞的Netty方式，同一连接线程安全。Redisson不仅提供异步非阻塞连接，还具备丰富的分布式工具，如分布式锁。

摘要由CSDN通过智能技术生成

jedis是同步阻塞式的，类似于Jdbc,是非线程安全的，多线程使用时需要使用连接池。

using Jedis in a multithreaded environment
You shouldn't use the same instance from different threads because you'll have strange errors. And sometimes creating lots of Jedis instances is not good enough because it means lots of sockets and connections, which leads to strange errors as well. A single Jedis instance is not threadsafe! To avoid these problems, you should use JedisPool, which is a threadsafe pool of network connections. You can use the pool to reliably create several Jedis instances, given you return the Jedis instance to the pool when done. This way you can overcome those strange errors and achieve great performance.

To use it, init a pool:

JedisPool pool = new JedisPool(new JedisPoolConfig(), "localhost");
You can store the pool somewhere statically, it is thread-safe.

JedisPoolConfig includes a number of helpful Redis-specific connection pooling defaults.