redis/jedis

Redis Java client

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 4th, 2026
Created on June 11th, 2010
Open Issues & Pull Requests: 122 (+0)
GitHub issues: Enabled
Number of forks: 3,919
Total Stargazers: 12,362 (+0)
Total Subscribers: 661 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 31.4 hours
Mean response time: 75.8 days
90th percentile: 150.2 days
Tracked items: 242

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 7 hours, while "feature" waits about 2 weeks. Only 7% of issues opened in the past year have been closed. Three people close 86% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 59
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 1,259 days
Stale 30+ days: 49
Stale 90+ days: 42

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 6
Events in 7 days: 12

Top labels

  • stale (34)
  • enhancement (33)
  • bug (25)
  • feature (18)
  • testing (17)
  • waiting-for-feedback (17)
  • maintenance (14)
  • discussion needed (11)

Detailed Description

Jedis is a Java client for Redis designed for performance and ease of use.

Jedis solves the problem of communicating with Redis servers from Java applications by providing a straightforward API for sending Redis commands. The client handles connection management and supports both single Redis instances and Redis Cluster deployments through separate connection classes. It implements the Redis Cluster Specification for clustered environments and includes support for all Redis data types including JSON and VectorSets. The tool also provides retry and failover capabilities, allowing applications to automatically switch between multiple Redis deployments when one becomes unavailable.

Jedis suits Java developers building applications that need direct Redis access without object-mapping abstractions. It works across a wide range of Java versions and maintains compatibility with multiple Redis versions. The README distinguishes Jedis from higher-level alternatives by noting that developers seeking object mapping should consider redis-om-spring instead, positioning Jedis as the lower-level choice for those who want direct command control. Teams should choose this tool when they need a performant, straightforward Redis client without additional abstraction layers.

The project maintains active support across multiple Java versions and Redis releases, with the most recent versions supporting Redis 7.2 through 8.10 and Java versions 8 through 25. Development activity shows consistent updates to track new Redis capabilities and maintain compatibility with current platform versions.