vertical-slice

Vertical slice architecture organizes code by feature so each capability is self-contained and easier to implement, test, and evolve. It eliminates the complexity of layered projects by keeping Request/Response types, Handlers, and Validators colocated within single-file slices.

To structure a feature slice, add a single file containing nested Command/Query, Handler, and Validator types. Use direct DbContext usage via MediatR handlers instead of repository abstractions, and register endpoint groups per feature in Program.cs for clean routing.

No, you should prefer direct DbContext usage with EF Core instead of broad repository abstractions. Vertical slice architecture encourages extracting shared code only after proven duplication, keeping feature logic self-contained without unnecessary wrapper layers.

Yes, you can register endpoint groups per feature in Program.cs. This approach provides clean routing and authorization boundaries for self-contained feature slices, ensuring each capability manages its own endpoints independently.

Vertical slice architecture organizes code by feature to reduce coupling and prevent architecture drift, whereas layered projects separate concerns horizontally. Slices keep feature logic colocated, simplifying feature delivery and testing compared to navigating multiple layered folders.

You should extract shared code only after proven duplication across feature slices. Vertical slice architecture minimizes shared dependencies intentionally, reducing coupling so that individual features like CreateOrder or GetOrder can evolve independently without broad refactoring.