kala

Man, how I wish Kala and Dcron would just work together. https://github.com/ajvb/kala https://github.com/victorcoder/dcron Fusing both would be AWESOME (I'd even like to help). What Dcron gets right: - Distributed by design - Raft for the reliable parts, gossip for lightweight sync, a match made in heaven - Linux mentality - Dashboard included - Good docs, nice website, looks serious What Kala gets right: - Built much more directly after Chronos, which has an amazing and battle tested API - Using ISO durations instead of NIHing their own format - Dependent jobs

Shouldn't be too hard. I threw in an issue to track it: https://github.com/ajvb/kala/issues/41

Kala is a simplistic, modern, and performant job scheduler written in Go. It lives in a single binary and does not have any dependencies. Kala was inspired by Chronos ( https://github.com/mesos/chronos ), developed by Airbnb, but the need for a Chronos for the rest of us. Chronos is built on top of Mesos, and is fault tolerant and distributed by design. These are two features which Kala does not have, as it was built for smaller deployments. It has a simple JSON over HTTP API, so it is language agnostic. It has a Web UI, Job Stats, Configurable Retries, uses ISO 8601 Date and Interval notation, Dependant Jobs, and is Persistent (using BoltDB). Any feedback would be much appreciated!