scylladb/scylladb

NoSQL data store using the Seastar framework, compatible with Apache Cassandra and Amazon DynamoDB

View on GitHub ↗Jump to charts ↓Open shareable report →

scylladb/scylladb has 15k+ stars and 1.5k+ forks on GitHub, is written in C++, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Server / PlatformCategory(s):NoSQL, Key-Value & CachesDatabases & Storage
Added to GitGenius on September 3rd, 2026
Created on December 24th, 2014
Open Issues & Pull Requests: 3,859 (+2)
GitHub issues: Enabled
Number of forks: 1,527
Total Stargazers: 15,792 (+3)
Total Subscribers: 330 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 52.1 days
90th percentile: 19.9 days
Tracked items: 4,323

Maintainer activity

74 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 10% of issues opened in the past year have never received a reply. 82% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 82% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. 68% of issues opened in the past year have been closed, leaving a working backlog. Three people close 58% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,404
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 792 days
Stale 30+ days: 1,341
Stale 90+ days: 1,283

Recent activity

Opened in 7 days: 0
Closed in 7 days: 2
Comments in 7 days: 37
Events in 7 days: 100

Top labels

  • symptom/ci_stability (810)
  • backport/none (618)
  • documentation (483)
  • triage/master (445)
  • bug (429)
  • area/tablets (418)
  • tests/flaky (382)
  • enhancement (355)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

ScyllaDB is a NoSQL data store that provides Apache Cassandra and Amazon DynamoDB compatibility.

ScyllaDB addresses the performance limitations of traditional Cassandra deployments by reimplementing the database in C++ using the Seastar framework, a high-performance asynchronous I/O library. This approach eliminates the garbage collection pauses and thread-per-connection overhead inherent in Java-based Cassandra, enabling significantly higher throughput and lower latency on the same hardware. The tool maintains wire protocol compatibility with both Cassandra and DynamoDB, allowing existing applications to connect without code changes.

Teams should consider ScyllaDB if they are running Cassandra workloads and want to reduce infrastructure costs through better per-node performance, or if they need DynamoDB compatibility without vendor lock-in. It suits projects with high-throughput requirements where latency consistency matters, particularly those already invested in the Cassandra ecosystem. Organizations can migrate existing Cassandra clusters to ScyllaDB by treating it as a drop-in replacement, since client applications require no modification.

The project maintains active development with regular commits across core database functionality, performance optimization, and compatibility features. Work spans the Seastar framework integration, query execution, storage engine improvements, and protocol implementation for both Cassandra and DynamoDB APIs. The codebase shows ongoing attention to test coverage and stability, with contributions addressing edge cases and production readiness.