The End of Layered Architectures with the Hexagonal Approach
summary
Explains why traditional layered architectures (MVC with Controller/Service/Repository and heavy use of annotations) can create code constraints and architectural limits. Presents the principles and mindset of hexagonal (ports-and-adapters) architecture and gives concrete examples and applicable scopes where hexagonal design can be effectively adopted.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 5:12Layered architecture issues
- 11:54Dependency problems
- 13:20Hexagonal architecture
- 16:50Ports and adapters
- 19:58Domain Driven Design
- 25:37Read/write separation
- 27:43Domain service interfaces
- 30:32Building adapters
- 31:57Configuration integration
- 33:24Hexagonal pros and cons
- 35:30When hexagonal fits
- 36:32Conclusion
- 37:17Q&A
related talks
45mThe End of Layered Architectures with the Hexagonal Approach
52mWhy not all hexagons have eight sides
46mHexagonal at Scale, with DDD and microservices!
01h 01mWhy not all hexagons have eight sides
51mHexagonal Architecture to the rescue
45mWhy Hexagonal and Onion Architecture Are Answers to The Wrong Question
15mHexagonal Architecture: How to Beat Spaghetti Code?
47mHexagonal Architecture Level 2: How to write well…