Spring Boot vs Quarkus: source lines of code compared

The Spring Boot vs Quarkus comparison on OctoCounts shows side-by-side source line counts for spring-projects/spring-boot and quarkusio/quarkus, 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 spring-projects/spring-boot and quarkusio/quarkus 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, spring-projects/spring-boot contains 397,436 total lines (247,475 code) across 4,946 files, while quarkusio/quarkus contains 1,303,463 total lines (969,178 code) across 15,611 files as of 2026-11-16. quarkusio/quarkus has about 3.9x the counted code lines of spring-projects/spring-boot 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.

Metricspring-projects/spring-bootquarkusio/quarkus
Files4,94615,611
Total lines397,4361,303,463
Code lines247,475969,178
Comment lines87,759171,492
Blank lines62,202162,793
Languages counted2122

Top languages in spring-projects/spring-boot: Java (87.1% of code), JSON (4.9% of code), JavaScript (3.5% of code). Top languages in quarkusio/quarkus: Java (75.9% of code), XML (14.4% of code), JavaScript (4.5% of code). Java, JSON, JavaScript, XML appear in both top language lists; YAML appears only in spring-projects/spring-boot's top languages; Kotlin appears only in quarkusio/quarkus's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. spring-projects/spring-boot was counted at ref main (commit 3d8ad8ecf389) on 2026-11-15; quarkusio/quarkus was counted at ref main (commit 62d5207e40a4) 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. spring-projects/spring-boot: 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. quarkusio/quarkus: 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: spring-projects/spring-boot is the Spring Boot repository — the convention-over-configuration framework layer on top of the Spring ecosystem, with its tests and documentation, in Java. quarkusio/quarkus is the Quarkus repository — the Kubernetes-oriented Java framework and its extension set, with its tests, in Java. Both repositories are JVM framework source trees, counted on the dates in the methodology line.

The per-language tables show Java dominating both counted trees, which makes this a like-for-like comparison of two framework codebases written in the same language and aimed at overlapping server-side workloads.

Repository size does not indicate framework performance, startup time, or memory use: those are properties of a built application and its configuration, not of the framework source tree's line count.

Sources: spring-projects/spring-boot repository · quarkusio/quarkus repository. 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, spring-projects/spring-boot or quarkusio/quarkus?

As of 2026-11-15, spring-projects/spring-boot contains 397,436 total lines (247,475 code) across 4,946 files, while quarkusio/quarkus contains 1,303,463 total lines (969,178 code) across 15,611 files as of 2026-11-16. quarkusio/quarkus has about 3.9x the counted code lines of spring-projects/spring-boot 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 spring-projects/spring-boot, quarkusio/quarkus, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. spring-projects/spring-boot was counted at ref main (commit 3d8ad8ecf389) on 2026-11-15; quarkusio/quarkus was counted at ref main (commit 62d5207e40a4) 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.