Nomad VS Dkron

[Nomad]

Lob’s core API has been fully migrated to HashiCorp's Nomad, Lob’s Next Generation service platform. This is a major milestone for the Nomad Project, the Platform Team, and Lob Engineering. This migration is the culmination of a year of R&D, months of practice migrating other Lob services, and weeks of work on this particular service. It’s absolutely worth celebrating for the complexity and customer impact.

Most of our API’s migration to Nomad happened in August, but the key feature of autoscaling was not working as expected. This turned out to be a bug in Nomad which James Douglas tracked down. The issue was recently fixed and autoscaling works as expected, completing the migration!

Nomad by HashiCorp

There's also https://pot.pizzamig.dev/ which even has a Nomad(https://www.nomadproject.io/) driver in case you want to "orchestrate" the jails(as in deploy many jails at the same time across multiple servers)

The check stanza runs a health check on the service Since the service is registered to Consul, the health check runs on Consul. The above health check is configured to run every 10 seconds, and is given 5 seconds for the health check query to succeed. Health checks in Nomad are similar to Kubernetes health checks.

Not sure if it fits here, and might be a little more complex than what you’re looking for, but Nomad is definitely worth a look.

I'd like to also mention hashicorp nomad + consul. They're worth evaluating.

Hashicorp Nomad

We had a hard time finding this data when experimenting with carbon aware scheduling in Nomad. There seem to be a lot of orgs working on this, but it’s all third party as far as I know. I couldn’t find a first party (eg Amazon, Microsoft, Google, etc) that provided this data via an API. Very frustrating.

There are a couple resources linked here: https://github.com/hashicorp/nomad/blob/h-carbon-meta/CARBON...

The silver lining is that the folks who are working in this space are extremely friendly and passionate in my experience. Don’t be scared to “contact sales for an API let.” The few folks I talked to were extremely helpful.

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.