The Kafka vs RabbitMQ comparison on OctoCounts shows side-by-side source line counts for apache/kafka and rabbitmq/rabbitmq-server, 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/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-11-16, apache/kafka contains 773,315 total lines (489,315 code) across 4,514 files, while rabbitmq/rabbitmq-server contains 375,778 total lines (258,795 code) across 1,935 files as of 2026-11-16. apache/kafka has about 1.9x the counted code lines of rabbitmq/rabbitmq-server 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.
| Metric | apache/kafka | rabbitmq/rabbitmq-server |
|---|---|---|
| Files | 4,514 | 1,935 |
| Total lines | 773,315 | 375,778 |
| Code lines | 489,315 | 258,795 |
| Comment lines | 198,366 | 63,127 |
| Blank lines | 85,634 | 53,856 |
| Languages counted | 14 | 30 |
Top languages in apache/kafka: Java (90.6% of code), Scala (4.2% of code), JSON (3.4% of code). Top languages in rabbitmq/rabbitmq-server: Erlang (69.4% of code), JSON (10.9% of code), Elixir (6.5% of code). JSON appears in both top language lists; Java, Scala, Python, XML appear only in apache/kafka's top languages; Erlang, Elixir, JavaScript, 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 1fd9dd580562) on 2026-11-16; rabbitmq/rabbitmq-server was counted at ref main (commit 346a51fdc985) 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/kafka: 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. rabbitmq/rabbitmq-server: 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.
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/kafka is the Kafka repository: the broker, the Java client, Connect, Streams, and their tests, with the server written in a mix of Scala and Java. rabbitmq/rabbitmq-server is the RabbitMQ server repository: the broker written primarily in Erlang, plus its core plugins and test suites. Both are message-broker source trees, but implemented in different languages, as the per-language tables above show.
The per-language tables make the implementation split legible at a glance: Kafka's counted code is predominantly Java and Scala, while RabbitMQ's is predominantly Erlang — each broker built on its language's concurrency model.
Each repository counts the broker core, but the scoping differs slightly: Kafka's client libraries and Streams live in the same tree, while part of RabbitMQ's plugin ecosystem lives in separate repositories, so the totals are not framed identically on both sides.
Broker repository size does not measure throughput, latency, or operational footprint — those depend on configuration, workload, and cluster topology. Use these counts to compare the size and shape of the two source trees, not to choose a message broker.
Sources: apache/kafka repository (broker, clients, Connect, Streams) · rabbitmq/rabbitmq-server repository (Erlang broker). 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.
As of 2026-11-16, apache/kafka contains 773,315 total lines (489,315 code) across 4,514 files, while rabbitmq/rabbitmq-server contains 375,778 total lines (258,795 code) across 1,935 files as of 2026-11-16. apache/kafka has about 1.9x the counted code lines of rabbitmq/rabbitmq-server 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.
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 1fd9dd580562) on 2026-11-16; rabbitmq/rabbitmq-server was counted at ref main (commit 346a51fdc985) on 2026-11-16. 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.