Coravel - Easy task scheduling for your .NET web apps

January 10, 2024 · 4 minute read · Tags: aspnet | blazor

Sometimes you need to run scheduled tasks for your .NET web app.

Automated report creation, status checks, routine admin tasks, that sort of thing.

I spent the last few weeks migrating Practical ASP.NET to .NET 8 (static SSR).

One requirement involved sending data to an external service.

For this I decided to keep things simple and rely on a crude mechanism to create records in a database table, then periodically check that table for records in order to send them on to the external service (via its API).

Historically, for this kind of task, I would have turned to Quartz.net, or possibly Hangfire.

But as I started to work on the requirement I remembered Coravel.

Coravel for easy task scheduling

Coravel is new to me, but from the GitHub repo looks to have been around for about 6 years or so (at the time of writing).

The docs are well worth a look as Coravel can handle a number of ’tricky’ tasks for your web app, including:

  • Task Scheduling
  • Queuing
  • Caching
  • Event Broadcasting
  • Mailing

For my specific case, I wanted to run a scheduled task on a regular basis to check the DB table and call the external API.

To make this work with Coravel requires an Invocable

public class SendEventsToThirdParty(
    AppDbContext dbContext, 
    ThirdPartyApi thirdPartyApi) : IInvocable 
{
    public async Task Invoke(){
        var events = dbContext.SyncEvents.Take(20).ToArray();
        await thirdPartApi.SendEvents(events);
        dbContext.SyncEvents.RemoveRange(events);
        await dbContext.SaveChangesAsync();
    }    
}

This is a straightforward C# class which implements IInvocable.

IInvocable requires us to implement the Invoke method.

To actually schedule the task there are two steps.

First, we need to register the invocable as a service.

Program.cs

 builder.Services.AddTransient<SendEventsToThirdParty>();

Then schedule it:

Program.cs

app.Services.UseScheduler(scheduler =>
{
    scheduler.Schedule<SendEventsToThirdParty>()
        .EverySeconds(30);
});

The fluent API has plenty of options for scheduling the task.

Coravel

Or you can use CRON if you prefer.

scheduler.Schedule<SendEventsToThirdParty>()
    .Cron()

With that, the task is scheduled, and will run every 30 seconds (so long as the web app is running).

In memory scheduling made easy

It’s worth noting this doesn’t persist the scheduled tasks anywhere, so there’s no mechanism to retry a ‘missed’ scheduled task if your app is down for a period of time.

In this case, with atomic operations being run every 30 seconds that isn’t an issue.

But if you do need task persistence/retries you can check out older, well established options such as Hangfire.

Otherwise, Coravel is a convenient, easy to use option.

A swiss army knife for your web app

Finally, Coravel has similarly straightforward APIs for other common background tasks, like caching, raising events, sending emails.

For example, in the same app, I need to use a third party service to generate a checkout link when someone goes to purchase a course/ebook.

Once a checkout link has been generated it can be used for every subsequent attempt to purchase a product.

So it makes sense to cache the generated link, and re-use it (at least for a period of time).

Here’s how I used Coravel to cache the checkout link, using an in-memory cache.

private async Task Buy()
{
    var checkout = await Cache
        .RememberAsync("SomeUniqueKey", CreateCheckout, TimeSpan.FromMinutes(60));
        
    NavMan.NavigateTo(checkout.data.attributes.url);
}

private async Task CreateCheckout() {
    // business logic to call third party API
}

The first attempt to assign a value to checkout will invoke the CreateCheckout method (because there’s nothing in the cache).

The result will be cached, so the next attempt will retrieve the cached entry (until the cache expires, after 60 minutes).

In Summary

Coravel makes it quick and easy to tackle scheduled tasks, and other common modern web app requirements.

You can create invocables for your key business logic, then schedule them using its scheduler, and use its simple APIs for other common tasks, like sending emails, handling events and caching data.

Join the Practical ASP.NET Newsletter

Ship better Blazor apps, faster. One practical tip every Tuesday.

I respect your email privacy. Unsubscribe with one click.

    Next up

    Interactive what now? Deciphering Blazor’s web app project template options
    Create a new Blazor Web App and you’ll be asked how you want interactivity to work, but what does it all mean?
    Should I put my Blazor components in the server project, or the client project?
    .NET 8 gives you a choice of projects, which one should you use?
    Share user authentication state with interactive WASM components
    Your server knows your user is authenticated, but what about your interactive WASM components?