querydsl 8
- Upgrading to Spring Boot 4, and finding out our LAZY was really EAGER because the entities were final
- Why the unread badge was wrong three times: from a client-side counter to a server count
- Getting entities out of the web app — splitting domain modules from API modules
- If nothing gets deleted, don't call it delete — soft deletes with a status column
- Spring Boot 2.7 to 3.3 and Java 11 to 21, in two steps
- An N+1 that IN clauses couldn't fix: when @OneToOne lazy loading can't create a proxy
- One method per condition is too many: a cursor-paginated dynamic query in Querydsl
- From 22 queries to 3: replacing a per-user offer lookup with a Querydsl IN clause