Our great sponsors
-
I would take a look at temporal.io. The website is kind of dogshit, I'd honestly use the wayback machine to read it from a few months ago because it used to have actual information on it. It's an uber-developed, cloud-native (i.e. kube) workflow engine with first class go support that has gotten some buzz and is pretty good. It's a clear replacement for hangfire, and I have verified that it does have cron support.
-
-
InfluxDB
Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.
-
-
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.
-
-
If you end up needing to build one. Check out this long running and well respective java project for ideas: https://github.com/quartz-scheduler/quartz