Airflow VS Cronicle

Contributing to Apache Airflow's open-source project immersed me in collaborative coding. Experienced maintainers rigorously reviewed my contributions, providing constructive feedback. This ongoing dialogue refined the codebase and honed my understanding of best practices.

In week Two, I contributed to the Apache Airflow repository.

Apache Airflow is an open-source platform to programmatically author, schedule, and monitor workflows. The platform features a web-based user interface and a command-line interface for managing and triggering workflows.

Airflow is the most widely used and well-known tool for orchestrating data workflows. It allows for efficient pipeline construction, scheduling, and monitoring.

AIRFLOW This is more of a library in my opinion, but Airflow has become an essential tool for scheduling in my work. All our ML training pipelines are ordered and scheduled with Airflow and it works seamlessly. The dashboard provided is also fantastic!

I agree there are many options in this space. Two others to consider:

- https://airflow.apache.org/

- https://github.com/spotify/luigi

There are also many Kubernetes based options out there. For the specific use case you specified, you might even consider a plain old Makefile and incrond if you expect these all to run on a single host and be triggered by a new file showing up in a directory…

You can try and contribute some new connectors/operators for workflow managers like Airflow or Airbyte

Wasn't it simpler to use Cronicle (https://github.com/jhuckaby/Cronicle)?

You can give cronicle a try. It has a web based UI and sone good stats.

Have a look at Cronicle ( https://github.com/jhuckaby/Cronicle )

Firstly, I tried Rundeck and Apache Airflow. They are complete overkill for what I want to do. Then I found Cronicle which is light enough, besides it can pull double duty as a general purpose scheduler.

Also check out http://cronicle.net/

Would recommend https://github.com/jhuckaby/Cronicle for anyone running cronjobs but would like to have an interface. It has plenty of features, logs, resource stats, and notifications. Plus it's easy to setup.

Thought I'd post here before taking a dive into this and see if anyone has any practical experience. I'm looking for centralising scheduled tasks for multiple servers, preferably with a management GUI for friendliness. I found Crontab-UI which seems to only interact with the single host's crontab. Then I stumbled upon Cronicle which looks feature rich but looks like multi-server is handled by deploying the GUI to each host. A central server + agents on each host would be nicer. I'm wondering if anyone uses Cronicle, or another solution? Thanks!