Imagine an asset and its lifecycle
There are two phases:
1. Loading asset in a code location -> It reads the metadata and sends it to the UI, which is saved in the state db
2. Somebody selects and clicks materialize (run) for an asset -> daemons are responsible for listening and running the function
There are two phases:
1. Loading asset in a code location -> It reads the metadata and sends it to the UI, which is saved in the state db
2. Somebody selects and clicks materialize (run) for an asset -> daemons are responsible for listening and running the function
Comments
1. We can attach tests to an asset
2. We can do declarative orchestration -> because one asset is one unit in the dagster