The Only .NET Scheduler You Should Be Using!

Hello, everybody, I'm Nick, and in this video I will introduce you to Hangfire. The best .NET library for task or job scheduling in .NET.

Don't forget to comment, like and subscribe :)

Social Media:

#csharp #dotnet

[Sirozha]

The title of the video sounds like a clickbait. I think you need a comparison video why is it better than other similar libraries, e.g. Quartz, Coravel, FluentScheduler.

[stochastic]

Quartz is extremely reliable and works very well. Hangfire is a very heavy dependency, I'd only adopt it if I really needed it.

[heischono]

Thanks for the video. Can you do a comparison of Hangfire, Coravel and Quartz, please?

[injenius]

Hangfire is solid but you should try Quartz. Over time I have replaced hangfire with Quartz in most of my projects. I find the extensibility and performance better

[ikenwakochukwudi]

It'll be nice to have a deep dive into hangfire

[AlphaZero-sf]

Please make a video to show all possible things we can do with Hangfire. I love your content so much.

[teisdraiby]

An in-depth video on Hangfire would be awesome!

[Abinton]

Could you make a comparison to Quartz. We are using Quartz but had some problems of scheduled Jobs that were never executed (due to a Bug I then fixed in v3.4). In addition we needed to extend a bunch of extra stuff. So, would be nice to know if there is another scheduling framework which is worth it switching.

[TheWoodad]

Have used Quartz, HF and Coravel and for me personally, choosing one over another depends on the environment and app requirements.

[anonymoos]

Perfect timing on this video! I am just starting to build an application that needs to execute tasks on a background service, with a follow-up n hours later AND have scheduled jobs. Hangfire looks to do all of that and includes a nice dashboard to boot. I will also look at some of the other libraries mentioned in the comments--Quartz, Coravel, FluentScheduler. Very excited I won't need to build from scratch :D

[ermanafacan]

I have used hangfire I generally like it. Dashboard is good but not properly documented how to secure it. Having multiple servers is a good benefit to scale.
dashboard security and scale with multiple servers are the next video post ideas from me. Perhaps it's good to mention about async await problem of it too

[margosdesarian]

Surely Nick you have played around with the scheduling options that you can build in .Net Core? What are the drawbacks that make you prefer Hangfire?

[PhilippFeigl]

While I love Hangfire and we also used it in various production environments, my by far biggest problem is that under the hood everything is static. While the surface looks nicely integrated into the .net service architecture, it actually really isn't. This makes it absolutely impossible to write reproducable integration tests because there is no way to reset the state of the objects.

[MatinDevs]

Thank you Nick for listening to us and making valuable videos again ❤

[ronaldmariah]

It's the first time I'm hearing of Insomnia. Is this what you prefer using over Postman or is there certain features Insomnia has over Postman that makes it better?

[DeadDad]

Wow! Awesome library! I will definitely be checking it out. Thank you Nick!

[brechtlaitem]

We also use this a lot in our projects. With some nice extension packages you can have progress bars in the dashboard wich is cool. The dashboard itself is useful, but if you have a lot of jobs that get triggered very often it can become cumbersome to find an invokation of certain job types. Some sort of filter on date or job would be nice.

[adrigorithm]

What do you mean "trust"? These are open source, you can look at the code. That being said if you want how everything works you should be using timers (and eventually roll your own scheduling system).

[theprantadutta]

Thank you a lot, you are not going to believe the timing of this video is inch-perfect.

[skitto]

This is my goto. Every client loves the dashboard features