Shrek, Onions and Architecture
summary
Claims that large monoliths become maintainable by treating them as onions and applying hexagonal architecture, with concrete steps: define core domain abstractions, implement ports and adapters, use repositories and dependency injection, prefer value objects and fakes over mocks, and run static checks with dep track. Recipes map to practice via the Salt Fat acid Heat rules: remove redundant comments, avoid bloat, enforce lifecycles, and test implementations. A migration attempt stalls until the monolith is understood and money is saved.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:10Legacy monoliths misunderstood
- 3:57Onion and hexagonal architecture
- 13:58Onions and domain-driven design
- 23:05Legacy code with Salt Fat Acid Heat
- 31:22Salt for code clarity
- 31:43Fat and bloat in code
- 40:31Complexity vs dependencies
- 47:08Testing legacy code with heat
- 48:55Summary
related talks
45mShrek, Onions and Architecture
47mShrek, Onions and Architecture
01h 29mArchitecture Beyond Clean & Hexagonal
51mA Contrarian View of Software Architecture
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
40mDDD, CQRS, Hexagonal, Onion,... Putting it together
42mStratified design and functional architecture
41mUsing Boundary-Driven Development to beat code complexity