Architecture Decision Records

Architecture Decision Records (ADRs) are documents that capture important architectural choices made on a project. This example ADR covers JPA fetch strategies in a Spring project: Open Session In View is disabled as an anti-pattern, all associations should be declared lazy by default, and JOIN FETCH in JPQL queries should be used explicitly when related data is needed. The post also covers handling duplicate results from JOIN FETCH using Hibernate query hints and appropriate return types like Set or LinkedHashSet.