Hello, I am using Dagster to orchestrate generatio...
# ask-community
s
Hello, I am using Dagster to orchestrate generation of text using LLMs. Each time the output is generated, it is different due to the inherent randomness in the generation process. Is it the best practice to use assets for this or ops? I want to generate the output and then store it in a DB, in addition to it being stored in a persistent file system. What should my computation graph look like? Should I materialize assets and then use ops to store it, or should storing be part of the asset function?
s
Hi Stepan - do you want to overwrite the previous output or write a new output each time?
If you want to overwrite, then assets are a good fit, and I would store it as part of the asset function, or delegate it to an IO manager
s
Hello sandy, thanks, I am overwriting it and storing it as part of the asset function is how I ended up implementing it 🙂
👍 1