Hangfire (https://hangfire.io) includes default exception handling and is very extensible, I think it's a good mid-level choice and a good alternative to other queue mechanism, if you can't afford to host a separated queue service or can't manage a separated service; also scales pretty well (you can have multiple servers handling the same background job queue, or different queues). It runs on Sql Server and MySql... Source: almost 2 years ago

I used to just use hangfire.io in .net and worked wonderfully for any long running tasks or schedules. Had a great queuing system, UI to know if they failed , etc. That's how I'd send emails, pdf's, and other things along that nature. Then if it were more just a db related operation, just setup a schedule in mssql job service. Source: about 2 years ago

You can use hangfire for cronjob, to run at a time in future, you can use Hangfire.Schedule(jobid, datetime). Source: about 2 years ago

So another option is to use something like https://hangfire.io to pull the jobs and process them? Source: about 2 years ago

I've got a fairly large process I need to handle in background on my .net core web app so I've exported it to a background task using Hangfire. Source: almost 3 years ago

Zuul (https://zuul-ci.org ) is specifically built for this use case. It was originally designed for OpenStack's CI, with OpenStack being broken down in multiple inter-dependent repos. Source: 6 months ago

If you’re already using gerrit I would strongly recommend looking at Zuul https://zuul-ci.org. Source: 11 months ago

Zuul (code) helps your team stop merging broken code -- the best kind of gatekeeping. - Source: dev.to / over 1 year ago

I wanted to share a package that I have created, and use, to interface the Zuul CI from Emacs. It offers completion for builds or buildsets, and implements a zuul-log-mode to browse the remote logs. Source: almost 2 years ago

Yay, yet another proprietary Zuul clone! 😶. Source: almost 2 years ago