Post History

The way I made this work is not very quick but might provide extra benefit in the future. I have added Hangfire support to the application and use its BackgroundJob enqueuing mechanism as follows:

## Plugging Hangfire

```
using Hangfire;
using Hangfire.MemoryStorage;

public void ConfigureServices(IServiceCollection services)
{
    // other initialization here
    ConfigureHangfire(services);
}

private void ConfigureHangfire(IServiceCollection services)
{
     // this can be replaced with another type of storage
     // for actual persistence, but it is enough for this example
     services.AddHangfire(opt => opt.UseMemoryStorage());
			JobStorage.Current = new MemoryStorage();
     }
}

public void Configure(IApplicationBuilder app)
{
    // other configuration here

    StartHangFireJobs(app);
}

protected void StartHangFireJobs(IApplicationBuilder app)
{
    app.UseHangfireServer();
    // this is optional, but it provides a nice dashboard to see all job runs
    app.UseHangfireDashboard();
}
```

## Actual usage 

```
public IActionResult ExportPTBContracts()
{
    // virtually anything can be called here     
    // and the DI will work as expected
    // BackgroundJob.Enqueue(() => _fooService.DoFoo());
    return Ok();
}
```

The main disadvantage is that a third-party library is used. However, it allows to easily check how the jobs actually ran (how frequent were called, how much it took, unhandled errors, etc). 

More information is provided by [Hangfire Docs](https://docs.hangfire.io/en/latest/getting-started/index.html).