Three frameworks of Redis: Jedis, Redisson, Lettuce

Jedis api online URL: http://tool.oschina.net/uploads/apidocs/redis/clients/jedis/Jedis.html

redisson official website address: https ://redisson.org/

redisson git project address: https://github.com/redisson/redisson

lettuce official website address: https://lettuce.io/

lettuce git project address :Https://github.com/lettuce-io/lettuce-core

Concept:

Jedis: It is a Java implementation client of Redis, which provides a more comprehensive support for Redis commands,

Redisson : Realize distributed and extensible Java data structure.

Lettuce: Advanced Redis client for thread-safe synchronization, asynchronous and responsive use, supports clusters, Sentinel, pipelines and encoders.

Advantages:

Jedis: Provides comprehensive Redis operation features

Redisson: Promotes users to separate their concerns on Redis, and provides many distributed related operation services, such as distributed locks. Distributed collections can support delayed queues through Redis

Lettuce: Mainly used in some distributed caching frameworks

Scalable:

Jedis: Use blocking I/O, and its methods The calls are all synchronous, and the program flow needs to wait until the sockets have processed the I/O to execute, and asynchronous is not supported. Jedis client instances are not thread-safe, so you need to use Jedis through a connection pool.

Redisson: The event-driven communication layer based on the Netty framework, whose method calls are asynchronous. Redisson's API is thread-safe, so you can operate a single Redisson connection to complete various operations

Lettuce: The event-driven communication layer based on the Netty framework, whose method calls are asynchronous. Lettuce's API is thread-safe, so you can operate a single Lettuce connection to complete various operations

Conclusion:

Recommended use: Jedis + Redisson