Shrek, Onions and Architecture
summary
Big legacy monoliths map to onion layers: presentation, application skin, fleshy domain services, core domain model and infrastructure roots. Advice is concrete: define ubiquitous language and value objects, replace vague handlers with specific interfaces, use ports and adapters and constructor injection, keep domain referencing only abstractions, prefer throwing exceptions over error strings, use DepthTrack to enforce layer boundaries, and test with anonymous classes rather than heavy mocks; use PHP constructor promotion and type hints to remove stale comments.
AI-written summary · about
chapters (10)
- 0:00Welcome
- 1:06Legacy monoliths via Shrek
- 4:16Onion anatomy and layers
- 12:09Onions, growth, and DDD
- 23:46Legacy monoliths cooking tips
- 25:10Salt for code clarity
- 33:25Code bloat reduction
- 39:50Dependency balance
- 44:48Testing under pressure
- 46:13Recap and closing
related talks
45mShrek, Onions and Architecture
50mShrek, Onions and Architecture
31mArchitecting Onion Style Without Making Your Eyes Water
27mConfessions of a Backend Developer
45mWhy Hexagonal and Onion Architecture Are Answers to The Wrong Question
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
40mDDD, CQRS, Hexagonal, Onion,... Putting it together
45mOnion, Hexagonal, Clean or Fractal Architecture? All of them, and more!