You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is fairly common for entities / agents in a workflow to use artifacts created and stored by other entities / agents in a previous step of a workflow. We can certainly build our own persistence using spring templates and any one of its supported datastores. But - is it advisable? Would Embabel persistence make this effort redundant; or are they two separate things built for entirely different purposes?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
It is fairly common for entities / agents in a workflow to use artifacts created and stored by other entities / agents in a previous step of a workflow. We can certainly build our own persistence using spring templates and any one of its supported datastores. But - is it advisable? Would Embabel persistence make this effort redundant; or are they two separate things built for entirely different purposes?
Beta Was this translation helpful? Give feedback.
All reactions