Need advice about which tool to choose?Ask the StackShare community!
Airflow vs Argo: What are the differences?
Concurrency Model: Airflow uses the Directed Acyclic Graph (DAG) model, where each task can depend on one or more tasks and can be executed in parallel. On the other hand, Argo adopts the Kubernetes way of orchestrating tasks using pods, allowing tasks to be executed in parallel within a single pod or on multiple pods.
Native Containerization: Argo comes with native support for containerization, allowing users to package their code and dependencies into containers using Docker or other containerization technologies. In contrast, Airflow does not have native containerization support, requiring users to handle containerization separately if needed.
Event-Driven Architecture: Airflow follows an event-driven architecture, where tasks are triggered based on events or schedules. It provides a centralized scheduler to manage task execution. Argo, on the other hand, follows a workflow-driven architecture, where tasks are executed based on the defined workflow constraints and dependencies. It uses a separate controller to manage workflow execution.
User Interface: Airflow provides a web-based user interface (UI) that allows users to easily monitor and manage their workflows. The UI provides visualizations of task dependencies, task logs, and other useful information. Argo, on the other hand, does not have a built-in web UI. However, it provides a command-line interface (CLI) and a REST API for managing workflows.
Native Kubernetes Integration: Argo is built specifically for Kubernetes and provides seamless integration with Kubernetes resources for managing and executing workflows. It leverages Kubernetes features such as pods, services, and persistent volumes to execute tasks. Airflow can also be deployed on Kubernetes, but it requires additional configuration and setup for integration with Kubernetes.
Community and Ecosystem: Airflow has a larger and more mature community compared to Argo. It has been around for a longer time and has a wider range of plugins and integrations available. This larger community and ecosystem provide better support and resources for users. Argo, being relatively newer, has a smaller community and ecosystem but is growing rapidly.
In Summary, Airflow and Argo have key differences in their concurrency models, native containerization support, architecture, user interface, Kubernetes integration, and community/ecosystem size.
I am so confused. I need a tool that will allow me to go to about 10 different URLs to get a list of objects. Those object lists will be hundreds or thousands in length. I then need to get detailed data lists about each object. Those detailed data lists can have hundreds of elements that could be map/reduced somehow. My batch process dies sometimes halfway through which means hours of processing gone, i.e. time wasted. I need something like a directed graph that will keep results of successful data collection and allow me either pragmatically or manually to retry the failed ones some way (0 - forever) times. I want it to then process all the ones that have succeeded or been effectively ignored and load the data store with the aggregation of some couple thousand data-points. I know hitting this many endpoints is not a good practice but I can't put collectors on all the endpoints or anything like that. It is pretty much the only way to get the data.
For a non-streaming approach:
You could consider using more checkpoints throughout your spark jobs. Furthermore, you could consider separating your workload into multiple jobs with an intermittent data store (suggesting cassandra or you may choose based on your choice and availability) to store results , perform aggregations and store results of those.
Spark Job 1 - Fetch Data From 10 URLs and store data and metadata in a data store (cassandra) Spark Job 2..n - Check data store for unprocessed items and continue the aggregation
Alternatively for a streaming approach: Treating your data as stream might be useful also. Spark Streaming allows you to utilize a checkpoint interval - https://spark.apache.org/docs/latest/streaming-programming-guide.html#checkpointing
Pros of Airflow
- Features51
- Task Dependency Management14
- Beautiful UI12
- Cluster of workers12
- Extensibility10
- Open source6
- Complex workflows5
- Python5
- Good api3
- Apache project3
- Custom operators3
- Dashboard2
Pros of Argo
- Open Source3
- Autosinchronize the changes to deploy2
- Online service, no need to install anything1
Sign up to add or upvote prosMake informed product decisions
Cons of Airflow
- Observability is not great when the DAGs exceed 2502
- Running it on kubernetes cluster relatively complex2
- Open source - provides minimum or no support2
- Logical separation of DAGs is not straight forward1
Cons of Argo
Sign up to add or upvote consMake informed product decisions
What is Airflow?
What is Argo?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Argo?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Airflow?
What tools integrate with Argo?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+14