Hacker News Reader

Comment by izyda | Hacker News Reader

Looks good. Very much looking forward to this being production ready. I am currently looking for a scheduler that provides a better UI/UX than cron alone.

Currently, what do you all use for this sort of thing?

Nextdoor has a not-yet-open-sourced solution: https://engblog.nextdoor.com/2015/06/10/we-do-not-run-cron-j... that looks great.

Does anyone have any experience with Yelp's tron? https://github.com/Yelp/Tron

View on HN

I work with @ajvb. We'll be working on getting this into production over the next 2 months. To do so, we'll be working on adding redis as a backend and making it distributable. The goal is to make it really easy to get started, but be able to scale out to bigger production systems easily.

@ajvb has plans for an awesome dashboard as well to complement this :) Stay tuned... good things ahead.

Is this associated with http://www.222labs.com ?

If not, is there an email or somehow I can PM you or @ajvb at?

We work together there. We actually both started working on a job scheduler independently, but joined forces and he ran with it. It's @ajvb's personal project, but we'll be using it at 222 labs for sure. You can shoot me an email at my username without the numbers @ gmail.com and I'll hook in @ajvb to the thread.

Please add postgres support.

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

With pleasure.

I had not seen Nextdoor's scheduler, which looks awesome except for the required external requirement of SQS. Kala was built to not require anything except for the Kala binary.

Yelp's Tron is awesome, but I wanted an JSON over HTTP API and ISO 8601 Duration Notation. Plus there are a few over problems with it that I currently don't remember.

Reply on news.ycombinator.com