apache/kvrocks

Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Type:Server / PlatformCategory(s):NoSQL, Key-Value & CachesDatabases & Storage
Added to GitGenius on September 15th, 2026
Created on August 15th, 2019
Open Issues & Pull Requests: 252 (+0)
GitHub issues: Enabled
Number of forks: 660
Total Stargazers: 4,435 (+0)
Total Subscribers: 82 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.9 hours
Mean response time: 20.7 days
90th percentile: 38.6 days
Tracked items: 271

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 16% of issues opened in the past year have never received a reply. 57% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. 70% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 54% of issues opened in the past year have been closed. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 106
New in 7 days: 4
Closed in 7 days: 1
Avg open age: 487 days
Stale 30+ days: 95
Stale 90+ days: 83

Recent activity

Opened in 7 days: 4
Closed in 7 days: 1
Comments in 7 days: 3
Events in 7 days: 18

Top labels

  • enhancement (147)
  • bug (94)
  • help wanted (58)
  • good first issue (38)
  • tracking-issue (4)
  • feature (3)
  • A-ci (2)
  • A-command (1)

Detailed Description

Apache Kvrocks is a distributed key-value NoSQL database that uses RocksDB as its storage engine and implements the Redis protocol.

Kvrocks addresses the need for a distributed key-value store that combines Redis protocol compatibility with persistent storage backed by RocksDB. Rather than storing data in memory like Redis, it leverages RocksDB's embedded key-value engine to provide durable storage while maintaining the same command interface developers expect from Redis. This approach allows applications written for Redis to work with Kvrocks while gaining the ability to handle larger datasets than memory alone permits and to persist data reliably across restarts.

Teams should consider Kvrocks when they need Redis-compatible semantics but require the persistence guarantees and storage efficiency of a disk-backed system. It suits projects where data durability is important and dataset size may exceed available RAM. The distributed architecture enables horizontal scaling across multiple nodes, making it appropriate for deployments that need both high availability and the ability to grow beyond single-machine constraints. Kvrocks is particularly relevant for organizations already invested in Redis tooling and client libraries who want to migrate to a more scalable, persistent alternative without rewriting their applications.

The project shows consistent development activity with regular commits across the codebase. Pull requests are reviewed and merged steadily, indicating ongoing maintenance and feature development. The project maintains active engagement with its issue tracker, addressing reported problems and feature requests. Documentation is kept current alongside code changes, reflecting a commitment to keeping guidance aligned with the implementation.