4 ms·
Exactly what I was looking for since months now! Loved the architecture of Chronos, but with JVM, Zookeper and Mesos as requirements, it had "heavyweight" writ
by endymi0n 11y ago
Exactly what I was looking for since months now!
Loved the architecture of Chronos, but with JVM, Zookeper and Mesos as requirements, it had "heavyweight" written all over the place. This is what the successor of cron should be IMHO. Distributed by design, API driven and dynamic.
EDIT: Apparently it's NOT distributed yet. Had hoped for Raft or etcd integration.
- samdolan805 11y agoFeel free to throw issues into the GH tracker so we can get them on the roadmap. My initial use case for this is for complicated time-based triggers that would be an absolute PITA/impossible to model in cron. We both felt the pain of setting up celery, etc.; @ajvb took that pain and put this together.
- thwarted 11y agohttps://github.com/erikh/jobd https://github.com/erikh/jobd uses etcd for distribution of jobs.
- ajvb 11y agoThe initial use case was for a single node setup, Chronos for an early stage startup. I/we will be adding support for it to be distributed here soon, but not until the single-node, single binary with no external requirements setup is production ready. If you have any feature requests, please create an issue in github. The more people request something the sooner it will get implemented. Thanks for the feedback though.