Blazor Server + Vertical Slice Architecture

Implement and evolve Blazor Server apps using vertical slices (feature-first), not layered architecture. Organize code by use case so each slice owns its UI, application logic, and data access. High cohesion inside a slice, low coupling between slices.

Target stack: modern .NET 8+ Blazor Server / Blazor Web App (Server). Prefer feature folders over Controllers/Services/Repositories layers. Avoid "god" services or generic repositories unless there is a proven cross-cutting need.

Project structure

• Top-level Features folder (or equivalent).
• Under Features, one folder per feature or use case:
  • Features/Users/GetUserList
  • Features/Users/UserDetails
  • Features/Events/ViewCreatedEvent
• Each feature folder contains everything specific to that use case:
  • Blazor components / pages (.razor, partial .razor.cs).
  • Request / command / query types and response / view models.
  • Handler(s) — MediatR request handlers or an equivalent application-service class — implementing the business logic.
  • Slice-specific helpers (mappers, validators) that are not truly cross-cutting.