Stop Using crond

on YouTube ↗22m

" summary

Cron is unsafe for nontrivial/business tasks; use a centralized scheduler like Rundeck integrated with Consul for service discovery so jobs run on live nodes by tags. Expose a REST API and UI that show schedules, history and metrics, and demonstrate a restore flow where a job produces a JSON list of backups and the UI offers dropdowns to pick a snapshot to restore; use systemd timers for simple ops and Prometheus for monitoring.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 3:18Cron requirements today
3. 4:02Rancher Jobs alternatives
4. 7:37Rancher with Consul
5. 11:35systemd-timers vs cron
6. 12:59When cron is acceptable
7. 14:24DevOps tools for teams
8. 15:49Q&A

" related talks

• 17mBuilding Robust Systems With ConsulMitchell Hashimoto · dotScale 2013
• 29mDeveloper-friendly jobs across time zones when "out of hours" no longer existsSuzannah Cooper · PyCon AU 2025
• 17mBuilding Robust Systems With ConsulMitchell Hashimoto · dotScale 2014
• 32mManaging CRDs and Operators in PracticeZhen Zhang, Wei Guo · KubeCon + CloudNativeCon Europe 2019
• 25mScalable IT Workload AutomationDieter Stubler · FOSSASIA Summit 2019
• 39mSell cron, buy Airflow: Modern data pipelines in financeJames Meickle · PyData DC 2018
• 31mThe Long, Winding and Bumpy Road to CronJob’s GAMaciej Szulik, Alay Patel · KubeCon + CloudNativeCon Europe 2021
• 28mDesigning for Failure: How to Manage Thousands of Hosts Through AutomationBrandon Bercovich · LISA18