Clean & Hexagonal Architecture - it really works!
summary
An open-source Labella app built with a Kotlin + Spring Boot backend and a Dockerized frontend demonstrates using Event Storming to design the domain and SVG templating for document output. The talk shows swapping Inkscape and ImageMagick renderers by changing a single factory line, a preview service composed from core plus a caching decorator, tests focused on messy implementation details, and that Spring Data REST delivered a quick (30-minute) CRUD; it concludes hexagonal/clean architecture helps evolve code but can be overkill for tiny throwaway projects.
AI-written summary · about
chapters (10)
- 0:00Clean & Hexagonal intro
- 6:49Why use Clean Architecture
- 10:47Clean Architecture flexibility
- 16:49Design patterns in Clean
- 21:40Hexagonal layers explained
- 27:22Hexa communication rules
- 32:18Benefits of both
- 35:49Q&A 1
- 39:01Q&A 2
- 44:10Closing
related talks
35mClean & Hexagonal Architecture - it really works!
47mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable
48mHexagonal Architecture in Practice, the Live Coding That Will Make Your Apps Plain... (live)
50mClean Architecture with Spring
50mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable
46mHexagonal Architecture in Practice That Will Make Your Applications More Sustainable
15mHexagonal Architecture: How to Beat Spaghetti Code?
48mLet's adopt the `clean archigonal`