All 15 Background Tasks & Hosted Services questions
More in Background Tasks & Hosted Services
How do you implement a periodic scheduled task using PeriodicTimer instead of Task.Delay, and what problem does it solve? How do multiple independently-registered BackgroundServices coexist within the same application, and does registration order matter? What is the difference between IHostedService and the BackgroundService convenience base class? How does IHostApplicationLifetime let a BackgroundService react to application startup and shutdown events? How does graceful shutdown work for a BackgroundService, and how should ExecuteAsync respect the CancellationToken? How would you implement a producer-consumer background processing pipeline using System.Threading.Channels alongside a BackgroundService? How would you implement a cron-like scheduled background job (e.g., 'run daily at 2 AM') without a third-party scheduling library? How do background services interact with health checks to signal their operational status to an orchestrator like Kubernetes? How would you implement retry logic with exponential backoff for a background service that calls a potentially-flaky external API? How would you implement a background task queue accepting ad-hoc work items dynamically at runtime, rather than a fixed polling loop?
Advertisement
ASP.NET Core › Background Tasks & Hosted Services

How would you configure a BackgroundService to fail fast and crash the host if a critical startup dependency (like a message broker) is unreachable?

Intermediate

Answer

If a background service absolutely cannot function without a dependency being available, throwing during StartAsync or the very first check in ExecuteAsync (combined with the appropriate BackgroundServiceExceptionBehavior.StopHost configuration) brings down the entire host immediately -- an intentional 'fail fast' pattern appropriate for genuinely critical dependencies, versus implementing a retry-with-backoff connection loop if brief startup unavailability should be tolerated instead of crashing.
builder.Services.Configure<HostOptions>(options => {
    options.BackgroundServiceExceptionBehavior = BackgroundServiceExceptionBehavior.StopHost;
});

protected override async Task ExecuteAsync(CancellationToken stoppingToken) {
    await _queueClient.ConnectAsync(stoppingToken);  // throws if unreachable -- crashes the host
}
Real-world example A payment-processing worker is configured to fail fast and crash immediately if it can't reach its message broker at startup, deliberately triggering a container restart and alert rather than silently running in a non-functional, degraded state.

Common follow-ups: When is 'fail fast' the wrong choice for a background service?;How does the default BackgroundServiceExceptionBehavior.Ignore differ from StopHost?

Hosting Models: Kestrel IIS & Reverse Proxies;Diagnostics & Performance
All 15 Background Tasks & Hosted Services questions