Jason Thomas
10/18/2022, 4:09 PM#prefect-2-orion
Hi all, question. Anything we can do in a @task
can also be done in a @flow
, but tasks have a limitation: they can’t call other tasks.
In a complex/nested job, for every function except the top-level flow I have to think about whether it is atomic and can be a task, or whether I will want to split it out further into multiple tasks, in which case it needs to be a flow.
But I realized I could just make everything a flow so I don’t have to worry about it. If I decide to split it out I can. If I don’t, no problem. Given the power and flexibility of flows, and that one arbitrary limitation of tasks, why use tasks at all?
So, what am I missing here? Are tasks obsolete? What’s their unique use case?redsquare
10/18/2022, 4:14 PMZanie
10/18/2022, 4:16 PMrun_deployment
).Anna Geller
10/18/2022, 4:23 PMJason Thomas
10/18/2022, 4:50 PM