This post is part of the 2018 C# Advent Calendar.

In the spirit of the season, we’ll be discussing how Santa Clause has recently been using .NET Core to build his internal Christmas present processing system.

Santa’s Needs

Santa is an intermediate developer but has been learning the ins-and-outs of .NET Core.

He recently needed to build a system that was robust in terms of security and ease of development.

He decided that .NET Core was the best choice when considering these criteria.

Santa didn’t want to re-invent the wheel - but he needed a reliable yet simple way to schedule background tasks, queue work so his web app was responsive (mostly for the elves), etc.

Coravel

One day he came across Coravel - which is a near-zero config open source library for .NET Core developers.

Coravel focuses on helping developers get their web applications up-and-running fast - without compromising code quality. It makes what are usually very advanced features super easy-to-use and accessible - without needing to install any extra 3rd-party infrastructure:

Task scheduling

Queuing

Caching

Event broadcasting

and more

Because it’s written specifically as a set of tools targeted for .NET Core, it takes advantage of native features - such as full support for the built-in dependency injection services and the hosted background services.

For example, you can inject dependencies/services into scheduled tasks, queued tasks, event listeners, etc. with zero fuss!

Santa has really enjoyed using Coravel - especially the time savings gained from not having to configure and install other dependencies for scheduling, queuing, event broadcasting, etc. individually.

He especially loves that Coravel ties into .NET Core’s DI system so seamlessly.

Drawback

But - now Santa has to schedule some really long running tasks. Tasks that might take hours to run. And these are important tasks.

Doing this inside his ASP .NET Core application is not an option since doing these types of long-running tasks in a web app will cause issues (as you probably know).

The Solution

Santa decided to check out Coravel’s GitHub repo - just in case this has been addressed before.

It turns out that there is a sample to address this exact concern!

I asked Santa if I could share how he decided to implement this. He agreed, but I was only permitted to show a very small sample of his system.

Scheduling Tasks From .NET Core Console Applications

One of the benefits of Coravel being specially for .NET Core is that it’s so simple to configure.

Combined with one of .NET Core’s coolest features, HostBuilder , and you can do some really powerful things in just a few lines of code.

The HostBuilder , by the way, let’s you construct a .NET Core application by adding just the specific pieces you need. Then you can “host” whatever you need (mini-API endpoints, console app running background tasks, or multiple hosted services) without the full dependencies needed for a typical web project.

Because Coravel is not a port of a .NET Framework library, but is specially built for .NET Core, Coravel’s features - such as scheduling and queuing - are implemented as a hosted services. This means Coravel is 100% compatible in non-web scenarios.

Using the sample mentioned above, let’s look at a very basic implementation of using HostBuilder along with Coravel’s scheduling:

class Program { static void Main ( string [ ] args ) { var host = new HostBuilder ( ) . ConfigureAppConfiguration ( ( hostContext , configApp ) = > { configApp . AddCommandLine ( args ) ; } ) . ConfigureServices ( ( hostContext , services ) = > { services . AddScheduler ( ) ; } ) . Build ( ) ; host . Services . UseScheduler ( scheduler = > scheduler . Schedule ( ( ) = > Console . WriteLine ( "This was scheduled every minute." ) ) . EveryMinute ( ) ) ; host . Run ( ) ; } }

This will be a console app that hooks into Coravel’s scheduler.

Every minute something will happen.

Supporting .NET Core Dependency Injection With Invocables

Ok - that’s a simple sample. Santa needs something more maintainable and he really needs to inject his Entity Framework Core Db context, HttpClientFactory , etc. into his scheduled tasks.

With Coravel you can use Invocable classes to solve this problem.

Invocables are ubiquitous classes that can be scheduled, queued, etc. with full support for .NET Core dependency injection. They represent some “job” in your application: Sending automated emails

Cleaning your database

Processing messages from an external queue

Syncing data between an external API and your system

Santa’s Invocables

Santa has an API that he uses to fetch who is nice and naughty (it’s a secret end-point from his legacy system). He then needs to do some CPU intensive processing to validate the data, and then store the results in his database.

He needs this done once every hour using the invocable classes he’s created.

scheduler . Schedule < PutNaughtyChildrenFromAPIIntoDb > ( ) . Hourly ( ) ; scheduler . Schedule < PutNiceChildrenFromAPIIntoDb > ( ) . Hourly ( ) ;

Problem With Scalability

Coravel internally uses Task.WhenAll to make sure async calls within scheduled tasks are processed efficiently.

However, CPU intensive tasks will “hog” the thread that is currently processing due tasks. This would force other due tasks to wait until the CPU intensive processing is completed.

This design makes sure that in web application scenarios Coravel won’t be hogging multiple threads that could otherwise be (and should be) used to respond to HTTP requests.

But Santa is specifically using a console application so he doesn’t need to worry about that!

What should he do?

Schedule Workers

Coravel solves this problem with Schedule Workers.

By using schedule workers Santa can put each of these tasks onto their own dedicated pipeline/thread:

scheduler . OnWorker ( "NaughtyWorker" ) ; scheduler . Schedule < PutNaughtyChildrenFromAPIIntoDb > ( ) . Hourly ( ) ; scheduler . OnWorker ( "NiceWorker" ) ; scheduler . Schedule < PutNiceChildrenFromAPIIntoDb > ( ) . Hourly ( ) ;

This will now execute each task in parallel so Santa can fetch and process both of these more efficiently. Any intensive CPU work that either task may perform will not cause the other to wait/block.

Schedule Task Groups

In some cases, you may want to put multiple tasks onto one worker and perhaps dedicate one worker for a task that is known to either take a long time or is just CPU intensive.

For example:

scheduler . OnWorker ( "EmailTasks" ) ; scheduler . Schedule < SendNightlyReportsEmailJob > ( ) . Daily ( ) ; scheduler . Schedule < SendPendingNotifications > ( ) . EveryMinute ( ) ; scheduler . OnWorker ( "CPUIntensiveTasks" ) ; scheduler . Schedule < RebuildStaticCachedData > ( ) . Hourly ( ) ;

The first two tasks don’t take that long to complete and are not a priority in terms of CPU usage (they are mostly I/O bound).

The second, however, needs to be able to work without being blocked or blocking other tasks.

This setup will ensure that RebuildStaticCachedData is always executed in isolation with it’s own dedicated pipeline.

Conclusion

I hope you’ve enjoyed this article and would love to hear from you in the comments! Maybe there’s a better way to do this? Maybe you simply prefer some other way?

New Site!

I’ll be writing new content over at my new site/blog. Check it out!

Keep In Touch

Don’t forget to connect with me on twitter or LinkedIn!

You Might Also Enjoy