Codebase architecture: layered, hexagonal, onion, clean and functional core
Five ways to organise backend code and the single idea behind them: dependency direction. Closed and open layers, ports and adapters, the domain at the centre, the dependency rule, DTOs at the boundary, repository interfaces on the inside, a pure core with I/O at the edges. Plus how to choose by project size and how to enforce it automatically with ArchUnit.