A high-performance Java client for Redis designed for ease of use and comprehensive Redis feature support.
Jedis is a Java client library for Redis, enabling Java applications to communicate with Redis servers efficiently. It provides a comprehensive implementation of Redis commands and data types, solving the need for a reliable, high-performance bridge between Java code and Redis data stores. The library supports advanced features like clustering, failover, and token-based authentication.
Java developers building applications that require Redis for caching, session storage, real-time analytics, or as a primary data store. It is particularly useful for teams working on scalable, distributed systems.
Developers choose Jedis for its proven performance, extensive Redis feature coverage, and straightforward API that reduces integration complexity. Its active maintenance, compatibility with multiple Redis and JDK versions, and strong community support make it a dependable choice over other Java Redis clients.
Redis Java client
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements all Redis commands and data types, including JSON and VectorSets, ensuring full feature coverage for complex use cases.
Supports Redis Cluster, failover mechanisms, and token-based authentication with Microsoft EntraID integration, making it suitable for production environments.
Compatible with Redis versions from 5.0 to current and JDK versions 8 to 21, as detailed in the compatibility table, reducing upgrade friction.
Backed by Redis with regular updates, extensive testing (codecov badge), and active Discord support, ensuring long-term viability.
Requires manual handling of Redis commands without built-in object mapping, pushing developers to use separate libraries like redis-om-spring for higher-level abstractions.
Key information is split between the README, external documentation site, and Javadocs, which can complicate onboarding and troubleshooting.
Setting up cluster connections or failover involves multiple steps and external references, increasing initial setup time and potential for errors.