Jobs that need retries, atomicity, monitoring, rescheduling, ad hoc scheduling, and flexibility probably aren't suited to most cron servers.

Beanstalkd, cronicle, agenda, sidekiq, faktory, celery, etc. are the usual suspects.

What is often missing is HA of the controller service process.

▲

sfortis 6 days ago | parent | next [-]

Chronicle is a lifesaver. HA, clustering, API, clean UI, it's doing everything right. I'm using this also as an API wrapper for Bash and Python scripts.

https://github.com/jhuckaby/Cronicle/blob/master/docs/Setup....

▲

mrweasel 5 days ago | parent | prev [-]

I'd probably even add systemd timers to that list. It does most of what you list, minus the retries (but I think you could handle that in the service definition)

▲

burnt-resistor 5 days ago | parent [-]

systemd doesn't scale beyond one system or have high availability.

	▲	sgarland 4 days ago \| parent [-]
		Do you know how many timers you could run on a single instance? An absurd amount.