A Clean, Pragmatic Architecture
summary
Argues that DTOs must not host business logic and that production systems use DTOs are evil by default, converting external JSON into immutable, validated domain objects; uses MapStruct for lightweight mapping and reports the approach in seven real projects. Recommends facades as thin orchestrators (keep them facade ~200-250 lines) that push complexity into domain services, and enforces boundaries with interface-in-domain adapters-in-infra plus Hibernate knowledge so entities can live in the domain and be fast, in-memory tested.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 2:20Data structures in architecture
- 12:29Logic and layered design
- 27:42Domain and adapters
- 34:03Database and pragmatic approach
- 41:11Clean architecture recap
- 45:44Anemic domain model
- 49:57Key takeaways and Q&A
related talks
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
01h 01mClean Architecture
56mDTO: Live Fast, Burn Bright
59mDomain-Driven Design - Where Rubber Meets the Road
01h 29mArchitecture Beyond Clean & Hexagonal
51mA Contrarian View of Software Architecture
47mHow to Structure Jakarta EE Applications for Productivity Without Bloat
48mDomain Driven Design: The Good Parts