vertical-slice-organization

Vertical slice architecture organizes .NET service folders by business capabilities instead of technical layers. This approach groups related functionality into feature-oriented folders, avoiding traditional technical directories to improve clarity and maintainability.

Structuring domain events in a Critter Stack service requires specific guidelines for organizing event files and their subscription handlers. The vertical slice approach keeps domain events aligned within their feature slice to maintain a clear and maintainable file structure.

Combining command handlers and validators in a single file is recommended for vertical slice organization. This single-file command approach groups the command, validator, and handler together, providing better understanding and easier maintenance within the feature slice.

Managing shared types across multiple vertical slices within the same service involves following specific guidelines for shared type organization. This ensures types are accessible across feature slices without breaking the vertical slice architecture boundaries.

Vertical slice architecture applies to .NET-based services using the Critter Stack, which specifically includes Wolverine, Marten, and Polecat libraries. These libraries work within the feature-oriented folder structure to maintain clear service organization.

Avoiding traditional technical folder structures in domain-driven design prevents splitting related features across disparate technical layers. Organizing by business capability instead keeps commands, handlers, and domain events cohesive within a single feature slice for better maintainability.