This page compares the source lines of code (SLOC) of apache/kafka and rabbitmq/rabbitmq-server 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, apache/kafka contains 757,461 total lines (480,371 code) across 4,465 files, while rabbitmq/rabbitmq-server contains 386,944 total lines (266,452 code) across 1,937 files as of 2026-09-08. apache/kafka is about 1.8x the size of rabbitmq/rabbitmq-server by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | apache/kafka | rabbitmq/rabbitmq-server |
|---|---|---|
| Files | 4,465 | 1,937 |
| Total lines | 757,461 | 386,944 |
| Code lines | 480,371 | 266,452 |
| Comment lines | 192,712 | 64,889 |
| Blank lines | 84,378 | 55,603 |
| Languages counted | 12 | 12 |
Top languages in apache/kafka: Java (90.5% of code), Scala (4.3% of code), JSON (3.3% of code). Top languages in rabbitmq/rabbitmq-server: Erlang (65.8% of code), JSON (10.6% of code), JavaScript (9.1% of code). JSON appears in both top language lists; Java, Scala, Python, XML appear only in apache/kafka's top languages; Erlang, JavaScript, Elixir, Makefile appear only in rabbitmq/rabbitmq-server's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. apache/kafka was counted at ref trunk (commit 20d81283e880) on 2026-08-26; rabbitmq/rabbitmq-server was counted at ref main (commit 76ff984fc61a) on 2026-09-08. 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.
apache/kafka has more code: 480,371 code lines versus 266,452 for rabbitmq/rabbitmq-server, about 1.8x as much, based on cached OctoCounts reports as of 2026-09-08.
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/kafka, rabbitmq/rabbitmq-server, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. apache/kafka was counted at ref trunk (commit 20d81283e880) on 2026-08-26; rabbitmq/rabbitmq-server was counted at ref main (commit 76ff984fc61a) on 2026-09-08. See the counting methodology for ignored directories and analysis options.
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.