Simplifying Our Code with Vertical Slice Architecture
summary
Claims a concrete path to make .NET codebases easier to reason about by replacing layered controllers/repositories with vertical use‑case slices that colocate handlers, data access and validation. Demonstrations use Martin Postgres event store and the Wolverine messaging framework, showing an incident‑tracking decider and a telehealth provider‑shift flow. Examples include transactional middleware, cascading messages, pure‑function decision logic, and a single‑roundtrip batched read with Martin; expectations are lower ceremony, easier unit tests, and incremental deployability.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:48Vertical slice architecture matters
- 5:00Vertical slice vs layered
- 9:15First vertical slice example
- 13:08Wolverine and ceremony
- 14:33Event sourcing with slices
- 17:02Validation and railway
- 19:09Open API benefits
- 20:14Code organization
- 21:36Complex data access
- 25:49Testing deep call stacks
- 26:10Q&A
related talks
01h 02mVertical Slice Architecture
54mDesigning for change with Vertical Slice Architecture
58mDesigning for change with Vertical Slice Architecture
40mSOLID Architecture in Slices not Layers
01h 29mArchitecture Beyond Clean & Hexagonal
51mA Contrarian View of Software Architecture
42mStratified design and functional architecture
44mBits and Pieces of a Great Architecture