DEV Community

Discussion on: Building A .NET Core 3 Scheduled Job Worker Service

Collapse
 
jamesmh profile image
James Hickey

Hangfire is def the defacto right now. Coravel was never built as a direct alternative, but many have pointed out that it's much easier to use.

Also, Coravel supports true async jobs, whereas Hangfire doesn't actually support true async jobs. So all that I/O in your background jobs will actually block your threads ðŸĪŠ.

See here for more

So, the answer to your question is "yes and no". There's an open issue here that I have on the todo list.

I offered a temporary/potential solution for now in that issue. Basically, you would just manage the tasks in a collection yourself. Coravel gives you some lower-level methods to start/stop any jobs you want (although, it's a workaround of sorts until there is an actual feature added 😂).