Architecting Onion Style Without Making Your Eyes Water
summary
An introduction to onion architecture for business-critical applications, explaining what the pattern is, how it maps to code, and how it compares to hexagonal and n-tier architectures. The talk starts from a real product need and shows how to decompose the system to preserve maintainability, resilience and quality while aligning with BDD-driven feature development.
AI-written summary · about
chapters (19)
- 0:00Introduction and presentation
- 2:00Hexagonal architecture and anarchy
- 3:18Focusing on the business
- 4:20The hexagonal
- 5:13Is it the same thing?
- 6:52Onion architecture
- 8:52Application layer
- 11:09Dependencies inward
- 13:04Domain and Infra
- 14:27Screaming Architecture
- 15:38The screaming architecture principle
- 17:13Behavior-driven development
- 19:12How to say it's too complex?
- 20:34The testing part
- 22:14The API part
- 23:45The useCase package
- 26:14The SPI package
- 27:24The rent module
- 30:19Conclusion
related talks
45mOnion, Hexagonal, Clean or Fractal Architecture? All of them, and more!
45mWhy Hexagonal and Onion Architecture Are Answers to The Wrong Question
51mA Contrarian View of Software Architecture
40mRecipe to go from Onion-Clean Architecture to Vertical Slice Architecture
52mExploring different architectural styles
51mDomain-centric? Why Hexagonal- and Onion-Architecture are answers to the wrong question
47mShrek, Onions and Architecture
54mArchitecture Is Not Nonsense