vertical-slice

Vertical slice architecture organizes code by feature rather than by layer, grouping endpoints, handlers, and validation into cohesive, self-contained units within feature folders.

Structure endpoints and handlers by placing them in dedicated feature folders, adopting a one-file-per-feature or per-operation pattern to encapsulate request, response, and validation logic together.

Shared concerns in vertical slice architecture should reside in Common/ or Shared/ directories to reduce cross-feature coupling while keeping individual feature slices isolated.

Yes, vertical slice architecture applies to both projects adopting VSA initially and existing projects adding new features, emphasizing scalable module boundaries and minimal cross-feature coupling.

Vertical slice architecture groups code by feature into self-contained slices, whereas layered architecture organizes by technical function, making vertical slices better for reducing cross-feature coupling.

Avoid vertical slice architecture if your project requires heavy cross-feature data sharing, as its design emphasizes isolated feature folders and shared concerns centralized in Common/ directories.