I think airflow ends up creating as many problems as it solves and kind of warps future development patterns/designs into its black hole when it wouldn't otherw

I think airflow ends up creating as many problems as it solves and kind of warps future development patterns/designs into its black hole when it wouldn't otherwise be the natural choice. There's the sort of promise of network effects -- "well of course it's better if /everything/ is represented and executed within the DAG of DAGs, right?" -- but it ends up being the case that the inherent problems it creates plus the externalities of using airflow for the wrong use cases start to compound, especially as the org grows. I think it slowly ends up being sort of isomorphic to the set of problems that sharing database access across service and ownership boundaries has, and my view is increasingly of the "convince me this can't be an RPC call, please" camp, and when it really can't (for throughput reasons, for example), "ok, how about this big S3 bucket as the interface, with object notification on writes?"