dotnet-background-services

To implement a .NET BackgroundService with graceful shutdown, use cancellation tokens to respect the host's stopping token and configure host shutdown timeouts to ensure safe cleanup during deployment or application termination.

The best way to handle background queue processing in .NET is using channel-backed work queues. This pattern enables scalable producer/consumer workflows with a singleton queue and a BackgroundService consumer that safely drains the queue.

IHostedService lifecycle ordering dictates that services start in registration order during startup and shut down in reverse order. This ensures dependencies are initialized correctly and cleaned up safely when the host stops.

You can use scoped services inside a .NET BackgroundService by creating a scope per work item. This avoids improper scoped service usage and ensures dependencies like Entity Framework contexts are resolved safely within the background worker.

A long-running worker tight-polls and causes high CPU usage when it lacks proper backoff strategies. Implementing error backoff strategies and using a PeriodicTimer prevents tight polling loops in background processing.

You do not need channels for periodic jobs in .NET hosted services if there are no producer/consumer workflows. Channels are specifically for scalable queue polling and work distribution, while periodic jobs only require a timer-based BackgroundService.