Why Hexagonal and Onion Architecture Are Answers to The Wrong Question
summary
Argues that hexagonal/onion patterns answer the wrong question: decoupling became a testability-era obsession and often produces incohesive code where a tiny change can touch 15 files. Recommends designing around vertical slices and hiding internals so surfaces stay small. Demonstrates Spring-era realities and IDE-driven packaging, and shows tooling like Spring Modulith and Amlecules plus Testcontainers and VS Code/Eclipse integrations to express modules and enforce encapsulation in code rather than folders.
AI-written summary · about
chapters (4)
- 0:00The problem with coupling
- 24:30Exploring popular archs
- 30:50Functional decomposition
- 37:31Architectural encapsulation
related talks
51mDomain-centric? Why Hexagonal- and Onion-Architecture are answers to the wrong question
47mThe End of Layered Architectures with the Hexagonal Approach
01h 01mWhy not all hexagons have eight sides
52mWhy not all hexagons have eight sides
45mThe End of Layered Architectures with the Hexagonal Approach
47mToo Many Mocks Kill the Test: What Hexagonal Architecture Changed
31mArchitecting Onion Style Without Making Your Eyes Water
48mLet's adopt the `clean archigonal`