there is orchestrator pattern + in Q3/Q4 we will work on supporting subflow-level infrastructure (I don't want to spoil too much but this is likely what you're looking for) https://discourse.prefect.io/t/how-to-create-a-flow-run-from-deployment-orchestrator-pattern/803

regarding Bob's advice on what's ready for production or not - I understand the sentiment but I believe everyone should consider the trade-offs and make a judgment based on your use case and your appetite for software - this post may help https://discourse.prefect.io/t/should-i-start-with-prefect-2-0-orion-skipping-prefect-1-0/544

The reason of why do we need to run each task on its own container is that we'd like to have a deployment with ETL like 1. extract data from sources and save it into some storage (Database or AWS S3 - here it does not matter) 2. transform the data in the storage by some patterns 3. load the transformed data into the final destination storage Though it's pretty common description, we the extract and the transform steps have pretty complex logic (sometimes with different package versions requirements) so it's much easier to put it into docker images. So the goal is not to pass a result-data between tasks, but to have one deployment which includes all required steps/tasks and to have an option to restart each task independent. Subflow here does not look like what we've been looking for.