Designing for change with Vertical Slice Architecture
summary
Claims from experience that reorganizing code into vertical slices — organize by use case — cuts coupling and keeps cohesion high, so features stay small instead of growing into 1k–5k line services. Shows concrete tools and patterns used: CQRS with Mediator-style handlers, Blazor UI, EF queries, queues/Kafka, and SQL or Cosmos trade‑offs. Describes building Enal’s claims product with faster iteration, early adopters and near-universal customer uptake, and reports onboarding time worsening to ~1 month (others hit 3 months) when layers create tangled services.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:07Change
- 3:47Architecture
- 12:05Complexity
- 14:05High Coupling
- 18:35Problems
- 20:45Solutions
- 26:10Advantages
- 28:50Use cases
- 31:45Easier to learn
- 32:45Easier to decompose
- 36:12Flexibility
- 38:24Application overview
- 44:56Vertical Slice Architecture
- 47:26Code Sharing
related talks
58mDesigning for change with Vertical Slice Architecture
26mSimplifying Our Code with Vertical Slice Architecture
01h 02mVertical Slice Architecture
40mSOLID Architecture in Slices not Layers
01h 02mBuilding that glorious monolith. And carving it too.
58mBuild software like a bag of marbles, not a castle of LEGO®
49mArchitecting Blazor applications – An Angular inspired approach
51mA Contrarian View of Software Architecture