vertical-slice

Vertical slice architecture is a .NET design pattern that organizes features into self-contained folders, preventing codebase degradation into hard-to-follow, layer-based structures by co-locating request, response, and handler logic together.

Structure feature folders by co-locating request, response, validation, endpoint mapping, and handler logic within a single feature directory, minimizing cross-feature coupling by centralizing shared concerns in Common or Shared locations.

Yes, you can replace traditional controllers and service layers with Wolverine conventions, source-generated Mediator patterns, or raw handler classes, keeping each handler focused on a single unit of work per use case.

Avoid cross-feature coupling by grouping endpoints per feature and forbidding direct feature-to-feature calls, centralizing shared code and common domain logic in dedicated Common or Shared folders.

The best way to add validation is through optional pipeline behavior patterns applied around handler-per-use-case structures, ensuring request validation logic executes cleanly within the feature slice.