How does the Generic Host support hosting multiple independent hosted services with different failure isolation needs?

Since each IHostedService/BackgroundService runs its own independent ExecuteAsync loop concurrently after startup, a failure in one (an unhandled exception, depending on BackgroundServiceExceptionBehavior configuration) doesn't necessarily crash unrelated hosted services running in the same host -- though by default an unhandled exception can still bring down the entire host in some configurations, so services with genuinely independent failure domains and criticality levels are sometimes better deployed as entirely separate processes/containers rather than combined into one host, trading operational simplicity (one deployable) against blast-radius isolation (one process's crash doesn't affect unrelated work).

// Two very different criticality services in the same host --
// a crash in one could still affect overall process health
builder.Services.AddHostedService<CriticalPaymentProcessor>();
builder.Services.AddHostedService<NiceToHaveAnalyticsExporter>();

// Consider separate deployments if their failure/scaling profiles genuinely differ