The Asset at Base Approach, Is It a Descriptive Approach?

One is at a far more declarative approach. In a task pace, orchestrator, you write a task, and it happens to produce an aset somewhere,. Then you have to manually insert it into a dag or flow or a job depending on the abstraction of the system that you're working in. You simply declare your asset, declare your upstin dependencies, and then the system kind of constructs that centralized dag in your behalf. It means there's no cause ifyo, if you're an airflow user, for example, or any otheryou would still mead to tell the system the order of sequence of events.