Hangfire VS QuartzNet

Hangfire is one of the most powerful background job processing libraries in the .NET ecosystem. Whether you're working with ASP.NET Core, .NET Framework, or integrating with Azure Services, Hangfire simplifies job scheduling, execution, and monitoring.

SignalR and .Net work so well together. We also heavily leverage Hangfire (https://github.com/HangfireIO/Hangfire) in our apps for any async/background processes as well.

Hangfire is a popular library for background job scheduling in .NET that provides support for recurring jobs, real-time monitoring, and persistent storage.

By following this guide, you have integrated Hangfire into your . NET 8 project and scheduled an API call using Hangfire with SQL Server as the storage provider. This setup ensures your API is called regularly according to the specified schedule. For more advanced Hangfire configurations and storage options, refer to the official Hangfire documentation.

6. Hangfire

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/

My personal favourite is Quartz.NET.

Quartz.NET is a full-featured job scheduling library that supports complex schedules, persistence, and clustering, making it ideal for enterprise applications.

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/