CommandScheduler 1.0.2

Integrate MediatR with Hangfire

To schedule your commands, execute them parallel with retry option and monitor them. Hangfire gives you all these kind of features but You have to have public method which You have to pass to Hangifre method (for example BackgroundJob.Enqueue). This is a problem – with mediator pattern You cannot pass public method of handler because You have decoupled it from invoker. So You need special way to integrate MediatR with Hangfire without affecting basic assumptions.

I presented the way of processing commands asynchronously using MediatR and Hangfire. With this approach we have:

1. Decoupled invokers and handlers of commands.
2. Scheduling commands mechanism.
3. Invoker and handler of command may be other processes.
4. Commands execution monitoring.
5. Commands execution retries mechanism.

These benefits are very important during development using eventual consistency approach. We have more control over commands processing and we can react quickly if problem will appear.

For this, In HSP.Infrastructure.Toolkits.CommandScheduler we difined 4 classes:

• CommandsScheduler serializes commands and sends them to Hangfire.
• CommandsExecutor responods to Hangfire jobs execution, deserializes commands and sends them to handlers using MediatR.
• MediatorSerializedObject wrapper class for serialized/deserialized commands with additional properties – command type and additional description.
• MediatorExtension extension methods for IMediator

public class MyMController : Controller
{
    private IMediator _mediator;
    
    public MyMicroserviceController(IMediator mediator)
    {
        _mediator = mediator;
    }
    
    [HttpPost]
    public async Task<IActionResult> Post([FromBody] TestCommand testCommand)
    {
     _mediator.Enqueue(testCommand);

      return Ok();
    }
  }

And our commands are scheduled, invoked and monitored by Hangfire.

Download source code

CommandScheduler is available on GitHub. https://github.com/AliBayatGH/CommandScheduler