The Easiest Scheduling for Your .NET Applications

Check out my courses on Dometrain: dometrain.com
Get the source code: mailchi.mp/dometrain/73q5eabiehm
Become a Patreon and get special perks: / nickchapsas
Hello, everybody, I'm Nick, and in this video, I will show you how you can implement easy scheduling for any type of .NET application in C#.
Give Coravel a star on GitHub: github.com/jamesmh/coravel
Workshops: bit.ly/nickworkshops
Don't forget to comment, like and subscribe :)
Social Media:
Follow me on GitHub: github.com/Elfocrash
Follow me on Twitter: / nickchapsas
Connect on LinkedIn: / nick-chapsas
Keep coding merch: keepcoding.shop
#csharp #dotnet

[@rk25412]

I have actually used Coravel in a small project in 2020, but we needed to save the schedule tasks to database so that they’d be loaded if the application is stopped or restarted, so we had to go hangfire

[@velkumars26]

Yes, I agree. I have also used it for small projects. It would be great if we can able to configure the task's from database or appsettings

[@behrad871]

It would be great if you create a video about the mailing feature. Thanks for sharing your knowledge

[@oswaldumeh8285]

It's been Hangfire for me for years now but this looks like something I'd like to try. It looks smooth and intuitive. Thanks for sharing, Nick.

[@alexandersuvorkin4213]

Sick library! Definitely will check it out. I'm using Quartz with manually written tasks api and config loader. Also SilkierQuartz UI for that

[@RicusNortje]

I have used both Quartz and Hangfire as I have aways needed the ability to cluster for high availablity. If the maintainer added a backplane persistance layer then I think many companies might consider this

[@adrianbennett2926]

My company also use both

[@ilyakurmaz]

Using it for a startup project and it works just fine (maybe with a few tricks)

[@Philippe42460]

Currently, we use Quartz. But thank you for showing Coravel, I'll try it when I have time. 👍

[@pedrosilva1437]

Coravel sounds very cool. I will have to give it a try for scheduling. And would love a video on how to also use it as a mailer.

[@karansingh-ku7yi]

very happy to know about evey functionaliy, Thanks

[@dojo85]

Cool video. Short and on point. Thanks :)

[@TedFanat]

Yesterday I faced a problem but then this video solved it. Nice

[@wabriones276]

We use hangfire as we need to store the schedules in the database. We have this ui to let users create their schedule, let hangfire deal with all the timezone shifts to dst and from dst.

[@luizrsjr10]

Awesome lib!!! just what I needed for my small pet project :)

[@local9]

Could of done with this yesterday! Time to add a refactor to the backlog

[@kennismaduka1728]

Now I don't have to go searching for a scheduler. Thanks Nick

[@antonzhernosek5552]

Dang, I literally was looking for a good scheduler the other day. This seem very interesting and honestly the biggest thing I'm interested in is being able to re-schedule things at runtime. Was skeptical about this being useful at the start of the vid, but the fact that you can inject a scheduler and prevent overlaps, looks very damn good

[@mwi1536]

Nice package. I was using Quartz (at least till today)

[@MetehanG]

Thanks Nick! Great video as always. For database saving purposes I guess it should be possible to capsulate a scheduler database schema based on ones requirements and create the Coravel schedulers on runtime based on this database records. I am more interested in how the task management works in the background. Is it like creating a single timer that ticks every n milliseconds and find any scheduled task that is due, or is it creating one independent timer per task? And also how is the memory management if I have too many (say 10000) scheduled tasks around? Well, time to experiment and figure out!

[@xtazyxxx3487]

Azure function with timer trigger is a good alternative also

[@leobottaro]

Hi nick, I love your videos and the way you teach. Do you have an in-depth course on ASP NET I can take part on? My main problem with most online courses and youtube tutorials is that those don't teach you how to structure an app for production, how to properly structure the database access, handle secrets, scaling, logging, monitoring, deployment and all that fun stuff. I know the basics, but now I want the in-depth profession info. I'd love an course/tutorial on that!

[@cdarrigo]

It's a nice solution as long as you only ever have one instance of the app doing the scheduling. There no coordination across instances to do things like prevent overlap

[@DasBloch]

This would be a good subject for @nickchapsas for a future video ! I too need something simple and moderne to handle this.

[@cheesypufs]

I rolled my own and needed distributed concurrency managing as well. Used Distributed Lock library to help with this.

[@serus164]

I was about to write that

[@oleglang5750]

Will you cover the overlapping with an example? Thank you!

[@ronsijm]

Interesting, I never heard of that Coravel scheduler. I generally just go with Hangfire. Curious about a more in-depth video about this scheduler, like how does it persist it's jobs, does it remember the last time it ran if you reboot, etc

[@nitrovent]

Nick mentions that there is no persistence.

[@Petoj87]

My goto is also Hangfire, combine it with hangfire.console and hangfire.console.extensions and it works great, but this seems a bit more lightweight and could have its uses when the application dosen't need all the functions of hangfire.

[@aemarco]

Hangfire is also my goto libarary, i guess persistance is yery often needed (also in my cases)....

[@stephenyork7318]

HangFire is such crap. I’ve had so many instances of setting a cron string to empty and it won’t remove the database entry. Then if with code to register my background process commented it still runs them because it uses database stored entries that weren’t cleared to use reflection to run the process. It’s so frustrating.

[@ronsijm]

@@stephenyork7318 if it's most people's go to scheduler and you're having huge issues with it, it doesn't really sound like it's the schedulers fault... What library do you use instead then?

[@ErnaSolbergXXX]

Even this is a nice package, things like this are super simple to make with async code. If we go back 20 years and the hassle it was to do multi threading for sure it would be nice with some package like this.

[@woaksie]

More on this library please

[@dev-on-bike]

used coravel in one of corporate projects and it fits nicely as a very lightweight job scheduler that accepts cron expressions. If us want to use more advanced stuff with scheduling (more user friendly like having UI) i would for sure switch to Hangfire. One downside of coravel as i remember is that issue when coravel can't resolve properly dependencies he silently skips this fact and u can end with not having executed your job logic.

[@SG_01]

I rolled my own scheduler for the application I work on, but mainly because I needed event scheduling rather than just simple task scheduling

[@1Eagler]

Event scheduling?

[@sinan720]

That just sounds like you needed a regular service bus like MassTransit

[@SG_01]

Yeah, like how you schedule events on a calendar. Create a series that starts at date X and lasts until Y, lasting a week and repeating every month kind of deal. Then receive callbacks to start and end, and potentially on application startup while it's going on.

[@eugenestein1629]

Awesome - clear and simple. Question - how would you deploy this to Azure?

[@mirkogeffken2290]

Nice!

[@TheAisoen]

Is it just for simplicity of use? Or does it have better performances than a background service checking the time?

[@kevinlloyd9507]

Hi Nick, love your videos. I have a question. How do you go about scheduling in an load balanced environment? Assume you have multiple services configured in an active/passive manner behind a load balancer. How do you allow only one service to kick off scheduling, but also still support failovers? Thanks man.

[@sachethana]

Nice video. Btw, Coravel's UI is paid. Quarts and Hangfire its free.

[@nickchapsas]

Hangfire has like 3 levels of paid tiers for Startups, Businesses and Enterprises.

[@yunietpiloto4425]

@@nickchapsasyou have most (if not all) of the features you demonstrated for this package in the free version of hangfire, plus, with the latter you get persistent jobs and a nice dashboard to manage tasks outside your application

[@robsosno]

Unfortunately storing state in database is important. This is because our application runs in multiple instances. Number of instances is not known in advance. We have to coordinate this instances and database seems to be good for this purpose.

[@notreadonly]

I guessed the right thing when I saw "easiest" in the title. I have been using it in my projects for 2 years it works flawlessly. But I don't recommend its cache library as it is not useful and doesn't refresh unless you flush it.

[@andyb012345]

Personally would rather just use Hangfire. This library seems to be charging for persistence support, while Hangfire has it out of the box. If you want to run jobs on a single machine, use the Hangfire memory storage abstraction.

[@metaltyphoon]

What’s the benefit of this over Quartz

[@porcinetdu6944]

How do you do that ? I was at the moment discussing with my bad about background tasks and a scheduled problem

[@tosunabi1664]

Is there any cleanup logic or OnStop event fired when web service is stopped?

[@PanSmierciYT]

Could you maybe compare this with Hangfire?

[@Zorxh]

Hangfire is a lot better (at least for free) due to it saving the jobs and queue in the database. Coravel does do a good job with naming and setup though

[@andreaskarz]

How can I stop a scheduler? Fox example, is start a scheduler, when the user logs out to send him a mail, that a product is in the basket. But this only for one week.

[@stephenyork7318]

What’s a practical example of when you would inject a scheduled task interface into an api endpoint to run something periodically? I can’t see why that would be a thing, your endpoint should finish quickly.

[@miroslavmakhruk4102]

Looks nice, but the good old System.Timer is pretty enough for me. 🙂

[@HugRunner]

It looks nice and intuitive, but web applications on many hosts, especially shared hosts, stop and start quite often, so it doesn't feel like this would be reliable for e.g. daily tasks if it cannot resume. But for applications you have full control over that they are running, I guess it could work.

[@alirezanet]

I still think Hangfire is much better for most of the usecases unless we're only dealing with fire and forget tasks in something like a console application

[@fritzfahrmann4730]

how to handle this with distributed containers?

[@trukeis856]

What if you have many instances of the same service

[@MrFreedomExpress]

can we add a schedular in asp core web app as well ?, your valuable suggestion is truly appreciated

[@krccmsitp2884]

Look at second example at 7:48

[@_miranHorvat]

Why are timers not good enough? But I actually prefere external triggering.

[@selmangulmez6476]

If i lost my pod connection thats it all tasks gone, need quartz for it for real. Any advice for quartz similar systems? Thanks.

[@nickchapsas]

Yes, use Hangfire

[@Chris-zb5nm]

Does it also have any storage? Because otherwise it wouldn't be that much usefull. An Scheduler must have an storage to save all schedules in case the app is restarted.

[@italofernandes6402]

That would be a good pull request 😉

[@antonmartyniuk]

Pro version of this library has a storage

[@viniciusmendonca7727]

so, if it does not support sharing database, I could not apply this in out scaled apps, right?

[@T___Brown]

You can use cron to configure in the db and pass to the cron function.

[@lukebennett3189]

What benefit does this have over say hangfire

[@maskettaman1488]

They seem like different use cases. Hangfire is persistent and distributed, this library is neither. If you just want some process within your service to run every hour then hangfire is very overkill for that

[@markrobinson5420]

I was loving this video until you said it doesn't have a database to store the schedules. That's a deal breaker for me unfortunately. I'm using Quartz at the moment, happy with it but the fluent API on this looked easier and more flexible. I need the schedule/events to be stateful though and survive a process shut down, my events need to run for months/years in some cases.

[@richarddeoude2572]

Didn't seem to be every two seconds though?

[@T___Brown]

I think it was video lag or compression

[@modernkennnern]

I don't like that they added an `IMailer`; it has nothing to do with scheduling. Do one thing, and do it right. Make another library - or a sub-package - if you want more stuff.

[@krccmsitp2884]

It actually *is* a separate NuGet package.

[@modernkennnern]

@@krccmsitp2884 oh. Fair enough then ^^

[@hobbit125]

If only Windows had a built-in scheduler that already did all of this with proper logging, etc... We could call it like "Windows Task Scheduler" or something.

[@kimandjasoninflorida]

Agreed. I don't see how this scheduler is needed. What happens when you need to modify the schedule?

[@krccmsitp2884]

That would be counter-productive since .NET Core is meant to be OS-agnostic.

[@zabralex85]

Hangfire is better, this is only for small things.

[@Th3MoL3]

First🎉

[@mad_t]

Holy sh** get out of my head! Stop reading my thoughts...