Pluralsight Course


Hangfire allows you to kick off method calls outside of the request processing pipeline in a very easy, but reliable way. These method invocations are performed in a background thread and called background jobs.

From the 10.000-feet view the library consist of three main components: client, storage and server. Here is a small diagram that describes the main processes in Hangfire:

Hangfire Workflow


Hangfire is not tied to the specific .NET application type. You can use it in ASP.NET web applications, non-ASP.NET web applications, in console applications or Windows services. Here are the requirements:

  • .NET Framework 4.5
  • Persistent storage (listed below)
  • Newtonsoft.Json library ≥ 5.0.1


You can create any kind of background jobs using Hangfire: fire-and-forget (to offload the method invocation), delayed (to perform the call after some time) and recurring (to perform methods hourly, daily and so on).

Hangfire does not require you to create special classes. Background jobs are based on regular static or instance methods invocation.

var client = new BackgroundJobClient();

client.Enqueue(() => Console.WriteLine("Easy!"));
client.Delay(() => Console.WriteLine("Reliable!"), TimeSpan.FromDays(1));

There is also more easy way to create background jobs – the BackgroundJob class that allows you to use static methods to perform the creation task.

BackgroundJob.Enqueue(() => Console.WriteLine("Hello!"));

The control is returned to a caller just after Hangfire serializes the given information and saves it to the storage.

Job Storage

Hangfire keeps background jobs and other information that relates to the processing inside a persistent storage. Persistence helps background jobs to survive on application restarts, server reboots, etc. This is the main distinction between performing background jobs using CLR’s Thread Pool and Hangfire. Different storage backends are supported:

SQL Server storage can be empowered with MSMQ or RabbitMQ to lower the processing latency.



Background jobs are processed by Hangfire Server. It is implemented as a set of dedicated (not thread pool’s) background threads that fetch jobs from a storage and process them. Server is also responsible to keep the storage clean and remove old data automatically.

All you need is to create an instance of the BackgroundJobServer class and start the processing:

using (new BackgroundJobServer())
    Console.WriteLine("Hangfire Server started. Press ENTER to exit...");

Hangfire uses reliable fetching algorithm for each storage backend, so you can start the processing inside a web application without a risk of losing background jobs on application restarts, process termination and so on.

Please use Hangfire Forum for long questions or questions with source code.