Full-depth report · Large modular Java
Spring Boot Architecture Report
Architecture Overview records the 1,026-package project map. Cycle Evidence and Hotspot Risk turn the model into short investigative lists. Subject Audit and Boundary Review examine one package. Current Investigation records the active view, Governance Audit records repository decisions, and the Evidence Appendix supplies capped detailed registers.
- Report packages
- 1,026
- Dependency edges
- 1,114
- Cycle groups
- 1
- Chapters
- 8
- Report date
- 31 Jul 2026
Why we included this report
We selected Spring Boot as the large-project case: the report contains 1,026 packages and 1,114 dependency edges. Architecture Overview covers the whole project, while its printable Matrix restores detail up to the 50-row ceiling, keeps the four-package problem cycle at exact package detail, and prints 20 dependency-bearing target columns at 98% scale. Later chapters narrow the evidence to one package.
We chose the configuration package because its dependency loop closes through four packages across nested boundaries. Subject Audit retains all four members of that loop, while Boundary Review separates the dependencies entering, leaving, and crossing the selected package.
Selected evidence
- Global architecture model with Architecture Overview, Cycle Evidence, and Hotspot Risk
- Subject Audit and Boundary Review for spring-boot-build.core.spring-boot.main:org.springframework.boot.context.properties.source
- Current Investigation and Governance Audit
- Short diagnostic lists that explain why each package or dependency was selected
- Evidence Appendix with at most 50 rows in each detailed register
Choose what you want to understand
If this is your first Architecture Report, start with Architecture Overview for the big picture. Then choose the question you care about; each description explains what that chapter will help you understand. Each link opens the chapter in the full report.
- 01 Architecture OverviewStart here to see how Spring Boot is divided into modules and packages, which areas exchange the most dependencies, and where dependency loops appear in the whole-project map.
- 02 Cycle EvidenceFollow the report's four-package dependency loop from the overview map into the exact package relationships that keep the cycle closed.
- 03 Hotspot RiskFind packages where changes may spread widely, then see whether the pressure comes from incoming dependencies, exposed code, or tightly connected internals.
- 04 Subject AuditZoom in on the selected configuration package and understand its immediate neighbourhood without losing the four-package cycle that reaches beyond it.
- 05 Boundary ReviewSee what calls into the selected package, what it calls out to, and which relationships cross its boundary before you change or split it.
- 06 Current InvestigationReopen the exact focused view behind this report, including its filters and highlighting, so you can continue the same investigation.
-
07
Governance AuditSee how the report compares recorded architectural decisions with current dependencies; this revision also makes clear that no decisions were recorded.
This Spring revision has no governance record to inspect. To see an owner-approved decision in its structural context, open the Simple Java Mail example. See Simple Java Mail’s representative Governance Audit
- 08 Evidence AppendixUse the capped package-metric and dependency registers when a deeper review or handoff needs more literal evidence than the short diagnostic lists.
What this report covers
- Source revision
- 1a5815cf3183a0c9493cece8ba550a6e8b125d67
- Licence
- Apache-2.0
- Language and evidence
- Java · compiled JVM bytecode from 261 production roots
- Project scope
- Production modules across the repository; two unstable compiler outputs excluded
- Report contents
- Whole project, focused package, current investigation, governance, and detailed evidence appendix
- Report date
- 31 July 2026
- AtlasArc version
- 1.0.0
How to use this case
Context here, evidence in the report
Use this page to understand the project snapshot and scope. Open the report to inspect the architecture chapters themselves.
View project sourceHow this example was prepared
-
Use the recorded source revision
Check out the Spring Boot revision linked on this page.
-
Build the production classes
Use JDK 21 and the project's Gradle 9.5.0 build. This example uses 261 production class roots and 8,030 compiled classes.
-
Choose the project evidence
Select the production JVM outputs and exclude the two compiler outputs that do not represent stable production modules.
-
Choose the report chapters
Include the whole-project chapters, the recorded org.springframework.boot.context.properties.source subject, Current Investigation, Governance Audit, and detailed evidence tables with a 50-row maximum.
Source and attribution
Open-source project. Pinned example.
Spring Boot is analyzed from the pinned source revision above under Apache-2.0 . The project name identifies the analyzed open-source snapshot; publication here does not imply affiliation with or endorsement by its maintainers.