DEV Community

Discussion on: Building A .NET Core 3 Scheduled Job Worker Service

Collapse
 
jamesmh profile image
James Hickey

Thanks for the feedback!

One of the issues it seems many devs run into with Window's task scheduler are, as you said, basic user permissions 😂.

Plus, if you want to move all your infrastructure to serverless / container services, etc. then with something like Coravel you literally have nothing to change. Using Windows Task Scheduler def. couples you to using a full VM or bare-metal infra.

And yes, Coravel Pro stores all the schedules in your DB so you can just change schedules on PROD with no deployments 👍

.NET Core 3 will have lots of cool stuff! Looking forward to it.