cron VS Dkron

Features - Supports Slack Apps using Socket Mode - Easy definitions of commands and their input - Built-in help command - Bot responds to mentions and direct messages - Simple parsing of String, Integer, Float and Boolean parameters - Customizable, intuitive and with many examples to follow - Replies can be new messages or in threads - Replies can be ephemeral, scheduled, updated or deleted - Supports Slash Commands and Interactive Messages - Supports context.Context - Supports middlewares & grouping of commands - Supports Cron Jobs using https://github.com/robfig/cron - Handlers run concurrently via goroutines - Full access to the Slack API github.com/slack-go/slack

You could this https://github.com/robfig/cron

This will print "Valid cron expression: */20 * * * *" to the console. You can find more information about this library, including installation instructions, on its GitHub page: https://github.com/robfig/cron

I used robfig/cron on each of the workers. I only had on the order of ~10 workers so polling was not an issue.

There are many excellent open-source projects on GitHub, where the code is transparent and available to everyone. As software developer, we can learn a lot from them including software engineering, unit testing, coding style standardization, etc. We can even find issues by looking into their code, and submit pull requests to contribute to tech communities. Today we are going to dig into the source code of a popular Golang open-source project on GitHub, robfig/cron, which is small and with clear annotations, and is very suitable for new developers to learn how to read and analyze source code.

Now let's implement the core of task scheduler, cron job. We will be using robfig/cron, a reputable cron library written in Go.

# Hello Everyone! Ive built this cronjob library after the trusted: https://github.com/robfig/cron.

I suggest this library.

You can take inspiration on cron lib, create a Job i's a function that you give a channel for quit action, and a probably cancel function (from background.WithCancel) for cancel running asynchronous task. You can have a scheduling worker if you decouple a great task to multiple job that listen to a channel that emit event.

Works great. Hope this helps. (For easiness GH here).

I'am also familiar to hangfire, used in the past as distributed job scheduler for Owin microservices in C# too. Btw when we moved towards Golang stack realized that hangfire wasnt really necessary. It was enough standard and idiomatic Go code, learning using Go Routine adding any Cron library and maybe a Redis dependency if persistence is needed. But if you really prefer something hangfire-like, give a try to https://dkron.io/ and its GitHub repo https://github.com/distribworks/dkron , it's pretty similar. They have an open source version but also a pro license, in the same way as hangfire does.

Perhaps https://dkron.io/ can solve your problem? Source at https://github.com/distribworks/dkron.