C#•16mo ago

✅ Background jobs, choosing the right library

Hello,
I need to implement a scheduled job that will be periodically executed.

Why are there so many libraries: Hangfire, Quartz, Coravel? Even .NET offeres the

BackgroundService

BackgroundService

BackgroundService

BackgroundService out of the box.

How do I choose the right library? Literally every one of them gets the job done...

Pobiega•9/2/24, 1:25 PM

They all have their own tradeoffs. Is it a one off, or do you have multiple jobs? What about multiple worker instances?

CoreOP•9/2/24, 1:38 PM

I would have multiple jobs, not just one. But each one would query the DB

Pobiega•9/2/24, 1:41 PM

Okay. What about an admin panel to run jobs manually etc? Is that something you need, or not relevant

Pobiega•9/2/24, 1:42 PM

And the amount of running instances question is still important

Pobiega•9/2/24, 1:42 PM

Ie, if you have three running instances, would it be a problem if all three ran the job?

CoreOP•9/2/24, 1:51 PM

I was thinking of usign distributed locking mechanism, so the task wouldn't be executed by multiple instances

Pobiega•9/2/24, 1:52 PM

That works. Otherwise, hangfire and quartz have that built in if wanted

Pobiega•9/2/24, 1:56 PM

I'd probably recommend go with coravel if you don't need manual triggering

CoreOP•9/2/24, 1:58 PM

Sorry, I forgot to mention that part, no GUI is needed, everything should be executed programmatically

PPobiega I'd probably recommend go with coravel if you don't need manual triggering

CoreOP•9/2/24, 1:58 PM

Thank you

Pobiega•9/2/24, 2:01 PM

There is an important caveat thou, coravel defaults to UTC

Pobiega•9/2/24, 2:02 PM

If you want to specify scheduled times in local TZ, don't forget to apply that modifier

CoreOP•9/2/24, 2:02 PM

I'm using Utc both in DB, and application

Pobiega•9/2/24, 2:02 PM

Ok, np then

CoreOP•9/2/24, 2:07 PM

Thanks again

✅ Background jobs, choosing the right library

Similar Threads

Similar Threads

Similar Threads