dotnet-core-expert

Structure the solution into Domain, Application, Infrastructure, and WebApi layers, then map endpoints with app.MapGet and app.MapPost in route groups. Handlers use MediatR's ISender to dispatch commands and queries, keeping endpoints thin and business logic in the Application layer.

Register JwtBearer authentication with TokenValidationParameters containing your issuer, audience, and signing key, then call app.UseAuthentication and app.UseAuthorization. Protect endpoints with RequireAuthorization() or named policies like RequireRole("Admin").

Commands implement IRequest<T> and mutate state through handlers that save changes via the DbContext, while queries are read-only requests that use AsNoTracking projections into DTOs. Both flow through pipeline behaviors for validation and logging.

Yes, EF Core provides ToListAsync, FirstOrDefaultAsync, and CountAsync for asynchronous execution. Pagination combines Skip and Take with a total count query, and AsNoTracking improves read performance by skipping change tracking.

Build a multi-stage Dockerfile producing a minimal runtime image, then create a Deployment manifest with livenessProbe and readinessProbe pointing to /health/live and /health/ready endpoints. Register checks with AddHealthChecks including database and Redis probes.

Clean architecture adds layering overhead that may not suit small prototypes, single-endpoint services, or short-lived utilities. For trivial CRUD apps, a single-project minimal API with direct EF Core calls can be simpler to maintain.