Evolving a Pragmatic, Clean Architecture A Craftsman's Guide
summary
Argues for continuous refactoring and a pragmatic Onion/Clean architecture: keep business logic in entities and domain services, expose separate DTO/read models (light CQRS), and map/validate at the application facade. Enforces the dependency inversion principle by defining interfaces in the domain and implementing adapters in infrastructure. Recommends pair programming, fitness functions and ArchUnit checks, warns about transaction boundaries when splitting a monolith, and cites pragmatic extraction from working systems (nine apps over five years at IBM).
AI-written summary · about
chapters (6)
- 0:00Start
- 1:17Continuous Integration
- 2:59Software Craftsmanship
- 6:52Protect the Developers
- 8:00Building Software
- 21:14Validation
