Indrivo.BackgroundProcessor.Utility.Service.Hangfire.PostgreSQL.Plugin 1.0.3

Background Processing

Introduction

During the development of multiple solutions @Indrivo we have ussually encoutered the need of having a background or ASYNCHRONOUS process that runs on different triggers like : cron expression, http trigger, message that came via a message bus etc. .NET Core comes with a basic functionality that covers the need of a background worker to some extent, however that is most often not enough and is pretty uncomfortable to develop and monitor.

Purpose

The main purpose of the module came from the need of a having MediatR run specific commands (long running requests) in the background asynchronously, known under the term Fire-and-Forget processes. As well the administrators would need to have a monitoring dashboard built on top of the functionality. Seamless integration and extension of MediatR functionality is desired. In time the module developed a way to run CRON jobs in a simillar fashion. So the main functionality right now consists of:

1. MediatR extension method for ASYNC processing -- .Enqueue();
2. Easy to use CRON job setup that can be integrated in projects that run with/without MediatR.
3. Monitoring dashboard for easier debugging and resolving of issues.

How to set up

Set up is pretty straightforward you will need to install the following packages inside your solution:

1. Indrivo.BackgroundProcessor.Utility.Contracts
2. Indrivo.BackgroundProcessor.Utility.Service.Hangfire
3. Indrivo.BackgroundProcessor.Utility.Service.Hangfire.PostgreSQL.Plugin
4. Indrivo.BackgroundProcessor.Utility.Service.Hangfire.SQLServer.Plugin

Each plugin comes with his own small installer. So you are free to use them explicitly. However the desired way is to add the following structure to your appsetting file. Example:

  "HangfireConfigurationOptions": {
    "DatabaseProvider": "SQLServer",
    "DatabaseConnectionString": "Server=(localdb)\\mssqllocaldb;Database=aspnet-hangfireTest;Trusted_Connection=True;MultipleActiveResultSets=true"
  }

Where the DatabaseProvider can be either of the : "SQLServer" | "PostregSQL".

Example of this setup can be seen in the reference web application present in the current repo.