When it comes to running background tasks in .NET Core, there are a bunch of choices available, ranging from the built-in and straightforward (BackgroundService) to more fully-featured NuGet packages (like HangFire) - but knowing which one is appropriate for your use case is not always obvious. Does your task need to run on a timer? Is it short-lived or long-running? What if your task fails? How do you best enable recovery for tasks that fail?

In this session, Spencer will break down the multitude of options for running background tasks in .NET Core. We'll discuss their advantages, disadvantages, use cases, ease of use, development experience, and more. By the end of the session, you'll have the information you need to make an informed decision about how you want to run your background tasks in .NET Core.

You will learn:

• Evaluate the trade-offs between built-in and third-party background task solutions (such as BackgroundService vs. Hangfire) based on feature requirements, complexity, and development experience.
• Match task characteristics to the appropriate execution strategy by analyzing whether your workload is timer-based, short-lived, long-running, or requires failure recovery.
• Implement resilient background task patterns that account for failure scenarios and enable reliable recovery in production .NET Core applications.