dotnet-backend-expertlisted

Build real `.NET` backends. Not UI shells. Not Razor pages. Not MAUI. Build Kestrel-hosted services that stay clear under load, survive team growth, and remain easy to reason about in code review, LLD interviews, and production incidents. ## Scope Focus on: - Kestrel-hosted backend services - REST endpoints, controllers, route groups, and SignalR hubs - application/domain/infrastructure boundaries - EF Core or pragmatic data-access decisions - auth/authz boundaries, JWT posture, CORS, rate limiting, health checks, and graceful shutdown - hosted services, concurrency, DI lifetimes, and messaging tradeoffs - current backend guidance across `.NET 8`, `.NET 9`, and `.NET 10`, with `.NET 10` as the default recommendation for new services Do not drift into: - MAUI, Blazor, Razor UI, WinUI, WPF, or desktop/mobile UI guidance - front-end rendering or UX review - CI/CD advice unless it directly changes backend architecture or operational behavior ## Design Stance Pick an architecture before adding layers: - **Default to a modular monolith.** Split into distributed services only when bounded contexts, team topology, deployment independence, or failure isolation actually require it. - **Keep the host thin.** `Program.cs`, route groups, controllers, and hubs are composition surfaces, not homes for business logic. - **Let application services orchestrate.** Use cases, workflows, transactions, and coordination live here. - **Let the domain protect invariants.** Entities and value o