Apache Hadoop VS Airflow

Did you check out tools like https://hadoop.apache.org/ ?

check out the various dockerfiles bundled with hadoop on GitHub. you can point to them from within docker-compose. they haven't been updated in a couple years tho.

There are different ways to implement parallel dataflows, such as using parallel data processing frameworks like Apache Hadoop, Apache Spark, and Apache Flink, or using cloud-based services like Amazon EMR and Google Cloud Dataflow. It is also possible to use parallel dataflow frameworks to handle big data and distributed computing, like Apache Nifi and Apache Kafka.

There are several frameworks available for batch processing, such as Hadoop, Apache Storm, and DataTorrent RTS.

A copy of Hadoop installed on each of these machines. You can download Hadoop from the Apache website, or you can use a distribution like Cloudera or Hortonworks.

The Apache™ Hadoop™ project develops open-source software for reliable, scalable, distributed computing.

So, clearly with your AP CS class and PLC logic knowledge, if you were dumped into a codebase like Hadoop, QT, or TensorFlow you'd be able to quickly and competently analyze what is going on with that code, understand all the libraries used, know the reasons why certain compromises were made, and be able to make suggestions on how to restructure the code in a different way? Because I've been programming for coming up on two decades and unless a system is within the domains that I have experience in, I would not be able to provide any useful information without a massive onboarding timeline, and definitely wouldn't be able to help redesign anything until actually coding within the system for a significant amount of time.

This requires the use of distributed computation tools such as Spark and Hadoop, Flink and Kafka are used. But for occasional experimentation, Pandas, Geopandas and Dask are some of the commonly used tools.

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