Clean Architecture with Spring
summary
Argues that Clean/Hexagonal Architecture is practical and shows a working Java Spring web app built around a register book use case that keeps domain logic in the center, uses explicit ports and adapters, and implements persistence with Spring Data JDBC and Lombok for wiring. Demonstrates input validation via self-validating command objects, options for mapping strategies, and enforcement with ArchUnit or separate JARs. Claims Spring stays noninvasive and the example compiles and runs as a small, testable prototype.
AI-written summary · about
chapters (29)
- 0:00Intro
- 0:18About me
- 1:20Layered Architecture
- 2:10Why bother with Architecture
- 2:30Goals of Architecture
- 2:57Making the software work
- 4:37Quality attributes
- 6:20Lifetime cost
- 7:34Layer Restrictions
- 8:17Database Driven Design
- 10:54Service Layer
- 11:58Layers
- 12:52Use Cases
- 14:31Cure
- 15:03Solid Principles
- 18:02Clean Architecture ID
- 20:40Single Responsibility
- 24:03DomainDriven Design
- 24:36Single Responsibility in Layers
- 25:37Service Use Cases
- 26:16Hexagon Architecture
- 28:13Triangle Architecture
- 30:43Package Structure
- 32:42Code Examples
- 32:59Register Book
- 36:22Register Book Service
- 38:45Business Logic
- 40:36Book
- 44:07Summary
related talks
23mClean Architecture? Clean Code? Refactoring? Tests? What does this change in my code?
50mAnatomy of a Spring Boot App with Clean Architecture
48mLet's adopt the `clean archigonal`
50mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable
46mClean & Hexagonal Architecture - it really works!
46mHexagonal Architecture in Practice
15mHexagonal Architecture: How to Beat Spaghetti Code?
47mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable