arch-review

An architecture review detects violations of clean architecture, hexagonal boundaries, and modulith constraints in Java Spring Boot modules by analyzing dependency direction, transaction boundaries, and event publishing, then producing a findings report with severity and remediation guidance.

Enforcing hexagonal architecture boundaries in a Java codebase requires auditing module dependencies to ensure they point inward toward the domain. A structured architecture review detects these boundary violations and generates remediation guidance to correct dependency directions.

ArchUnit works with Spring Boot modulith constraints by providing static checks to validate architectural rules. An architecture review leverages ArchUnit if available, supplementing it with file-by-file analysis to detect dependency direction and transaction boundary violations.

Generating a fix-plan workflow for architectural code defects requires a findings report that includes severity levels, affected files, and remediation guidance. An architecture review outputs this structured report with ticket skeletons to drive subsequent remediation tasks.

Domain model safety violations in Java Spring modules occur when dependencies bypass hexagonal boundaries or transaction boundaries are improperly managed. An architecture review detects these design violations through file-by-file analysis and static checks using ArchUnit.

You can audit transaction boundaries and event publishing in a Java module automatically through an architecture review. It performs file-by-file analysis and applies static checks via ArchUnit to identify violations and output a structured findings report.