Minimal API without persistence Use for a focused endpoint surface that does not own durable data or require caller identity.
dotnet new dotnet-service -n PublicApi --api-style minimal --data-provider none --database-provider none --authentication none --authorization none Controllers + PostgreSQL Use when the service owns relational data and conventional controller routing fits the API.
dotnet new dotnet-service -n OrderService --api-style controllers --data-provider efcore --database-provider postgresql Controllers + SQL Server Use when the service owns relational data in an environment standardized on SQL Server.
dotnet new dotnet-service -n CustomerService --api-style controllers --data-provider efcore --database-provider sqlserver Minimal API + SQLite Use for a small service or local deployment that needs owned relational state without an external database server.
dotnet new dotnet-service -n CatalogService --api-style minimal --data-provider efcore --database-provider sqlite Hosted service without a business API Use for scheduled or continuous work. Health endpoints remain available for operation.
dotnet new dotnet-service -n ReconciliationWorker --api-style none --job-processing hosted-service --data-provider none --database-provider none HTTP integration + OpenTelemetry Use when the service calls another HTTP service and needs distributed traces across the request path.
dotnet new dotnet-service -n PricingService --integration http --observability opentelemetry --data-provider none --database-provider none