First off, great article. I think airflow might have stemmed/been inspired from the implementation of Apache Oozie and hence there was a design decision to couple orchestration with runtime implementation of the tasks themselves _on the same node_. This has been one of Oozie’s fallacies.

So, this distributed approach was something I hoped _was_ the default, where one would be able to deploy operators on remote nodes.