ClickHouse vs Druid: source lines of code compared

This page compares the source lines of code (SLOC) of ClickHouse/ClickHouse and apache/druid 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-08-26, ClickHouse/ClickHouse contains 2,991,216 total lines (2,308,757 code) across 10,924 files, while apache/druid contains 1,188,413 total lines (849,185 code) across 7,035 files as of 2026-08-26. ClickHouse/ClickHouse is about 2.7x the size of apache/druid by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.

MetricClickHouse/ClickHouseapache/druid
Files10,9247,035
Total lines2,991,2161,188,413
Code lines2,308,757849,185
Comment lines259,575223,335
Blank lines422,884115,893
Languages counted1212

Top languages in ClickHouse/ClickHouse: C++ (63.5% of code), C Header (17.1% of code), GNU Style Assembly (11.8% of code). Top languages in apache/druid: Java (76.0% of code), JSON (8.6% of code), TSX (6.0% of code). C++, C Header, GNU Style Assembly, Python, C appear only in ClickHouse/ClickHouse's top languages; Java, JSON, TSX, TypeScript, XML appear only in apache/druid's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. ClickHouse/ClickHouse was counted at ref master (commit a36db2d1ade0) on 2026-08-26; apache/druid was counted at ref master (commit 1ed7baae5cb8) on 2026-08-26. See the counting methodology for ignored directories and analysis options.

Evidence and next steps:

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, ClickHouse/ClickHouse or apache/druid?

ClickHouse/ClickHouse has more code: 2,308,757 code lines versus 849,185 for apache/druid, about 2.7x as much, based on cached OctoCounts reports as of 2026-08-26.

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 ClickHouse/ClickHouse, apache/druid, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. ClickHouse/ClickHouse was counted at ref master (commit a36db2d1ade0) on 2026-08-26; apache/druid was counted at ref master (commit 1ed7baae5cb8) on 2026-08-26. 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.