Argo is extremely capable at its focus — coordinating workflows on Kubernetes. I had used Airflow for a few years, and looked into Prefect; in retrospect I'm v

Argo is extremely capable at its focus — coordinating workflows on Kubernetes. I had used Airflow for a few years, and looked into Prefect; in retrospect I'm very happy we chose Argo. Use Argo if: - Your tasks are containerized. - You're using Kubernetes, and can benefit from what it can offer — individually sized containers, autoscaling, fault-tolerance. - You have loosely coupled tasks — which pass at most pass files to each other, rather than python objects. - You don't have tens of thousands of tasks / streaming / etc. Airflow can run on Kubernetes, but with Airflow we ended up having equally sized workers up 24/7 — whether or not it was running an expensive job, a query on a remote system, or nothing.