Cassandra vs ScyllaDB: source lines of code compared

The Cassandra vs ScyllaDB comparison on OctoCounts shows side-by-side source line counts for apache/cassandra and scylladb/scylladb, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

This page compares the source lines of code (SLOC) of apache/cassandra and scylladb/scylladb using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.

As of 2026-11-15, apache/cassandra contains 822,872 total lines (545,786 code) across 3,572 files, while scylladb/scylladb contains 567,097 total lines (416,036 code) across 2,026 files as of 2026-11-16. apache/cassandra has about 1.3x the counted code lines of scylladb/scylladb under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Metricapache/cassandrascylladb/scylladb
Files3,5722,026
Total lines822,872567,097
Code lines545,786416,036
Comment lines176,22580,124
Blank lines100,86170,937
Languages counted1416

Top languages in apache/cassandra: Java (95.1% of code), SVG (2.1% of code), Python (1.6% of code). Top languages in scylladb/scylladb: C++ (61.9% of code), C++ Header (27.0% of code), Python (4.7% of code). Python appears in both top language lists; Java, SVG, XML, Shell appear only in apache/cassandra's top languages; C++, C++ Header, JSON, C Header appear only in scylladb/scylladb's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. apache/cassandra was counted at ref trunk (commit 30b73cadf345) on 2026-11-15; scylladb/scylladb was counted at ref master (commit 9d19bc68f8d6) on 2026-11-16. See the counting methodology for ignored directories and analysis options.

Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. apache/cassandra: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. scylladb/scylladb: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.

About this comparison

Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: apache/cassandra is the Cassandra repository: the wide-column database engine, predominantly Java, with its query language layer and extensive test suites. scylladb/scylladb is the ScyllaDB repository — a database written in C++ that implements the Cassandra query language and protocol family. The two databases share a protocol and query-language lineage but are independent implementations, counted on the dates shown above.

The per-language tables state the architectural difference in one glance: Cassandra's counted code is predominantly Java, while ScyllaDB's counted code is C++ — different implementation languages for databases that speak the same query-language family.

Same query language does not mean same codebase or same behavior under load: these are independent implementations, and repository size is a property of each project's source tree — it does not measure throughput, latency, or operational characteristics.

Sources: apache/cassandra repository · scylladb/scylladb repository (C++ implementation). Statements verified 2026-09-16.

Evidence and next steps:

Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

Compare FAQ

Which has more lines of code, apache/cassandra or scylladb/scylladb?

As of 2026-11-15, apache/cassandra contains 822,872 total lines (545,786 code) across 3,572 files, while scylladb/scylladb contains 567,097 total lines (416,036 code) across 2,026 files as of 2026-11-16. apache/cassandra has about 1.3x the counted code lines of scylladb/scylladb under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Does more source lines of code mean more complexity?

Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for apache/cassandra, scylladb/scylladb, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. apache/cassandra was counted at ref trunk (commit 30b73cadf345) on 2026-11-15; scylladb/scylladb was counted at ref master (commit 9d19bc68f8d6) on 2026-11-16. See the counting methodology for ignored directories and analysis options.

Can I compare a different branch, tag, or commit?

Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.