Designing for change with Vertical Slice Architecture
summary
Vertical Slice Architecture claims to replace layered projects by organize by use cases, putting UI, logic and data for a feature in one folder so changes stay local and coupling drops. Practical tools include Mediator/CQRS for request/handler wiring and a strict “no shared code by default” rule with the rule of three to extract shared logic. At enable this enables parallel V2 builds, faster iterations, easier onboarding (weeks not months) and simple cleanup by deleting feature folders.
AI-written summary · about
chapters (16)
- 0:00Welcome
- 2:32Change as core challenge
- 4:57Layered architecture limits
- 9:12Commercial pressures break layers
- 14:11High coupling root cause
- 21:58Vertical slice architecture
- 24:48Code sharing harms maintainability
- 28:04Coding for what you know now
- 30:16Optimal feature design
- 32:00Developer productivity boost
- 35:55Independent feature scaling
- 37:41New code is fun
- 39:07Commercial pressures handled
- 43:03CQRS with vertical slices
- 49:40Code sharing in verticals
- 57:23Final takeaways
related talks
54mDesigning for change with Vertical Slice Architecture
40mSOLID Architecture in Slices not Layers
01h 02mVertical Slice Architecture
26mSimplifying Our Code with Vertical Slice Architecture
48mUnderstanding Feature-Sliced Design
51mA Contrarian View of Software Architecture
32mFull stack architecture
50mTowards an Evolutionary Architecture