Hangfire VS QuartzNet

Unpopular opinion incoming... What I see is yet another way that the backend JS world is finally achieving something .NET had years ago[0].

Node/Deno/Bun/etc. + npm sounds super straightforward at first glance (and it is at first). But I've thought for years that it's far easier to be productive as an organization on .NET in Visual Studio, since it's simpler to design, deliver, and maintain infrastructure.

[0] https://www.hangfire.io/

you can read about it here HangFire Documentation

I mostly work in .NET, and typically use Hangfire, but all languages has similar frameworks

Its hard to tell what tool would be a best fit without more information, but I would suggest looking at Hangfire for background job processing: https://www.hangfire.io/

You might want to look at https://www.hangfire.io/. Their docs explain how to set up queues: https://docs.hangfire.io/en/latest/background-processing/configuring-queues.html

In this article we looked at how to use Hangfire to schedule background jobs in ASP.NET according to our requirements. In a follow up article, I will talk about using Hangfire with a Redis storage. To learn more about Hangfire, you can visit the official website.

Easy to understand if you want to implement your own background service. If you want a more easy and complete tool you can use hangfire.

Try https://www.hangfire.io/

If, as you stated, you really need to use your own servers, that seems exactly like a job for Hangfire.

I would agree with using Job over Queue. Therefore I would recommend looking at Quartz.Net https://www.quartz-scheduler.net/

You can use something like https://www.quartz-scheduler.net/ to create multiple recurring jobs based on the definition you load from a DB.

Or use an existing open source scheduling solution like https://www.quartz-scheduler.net/

If you're interested in using Quartz, you can check out their GitHub repo here: https://github.com/quartznet/quartznet. They also have extensive documentation available on their website: https://www.quartz-scheduler.net/documentation/index.html.

You should use an actual scheduler. https://www.quartz-scheduler.net/

Better to use a framework like Quartz.NET for scheduling background tasks. How it works inside the box I have no idea, but I have used it extensively in my web applications, and those background tasks run 24/7, come hell or high water. It's a good library, and it's easy to use.