Persistency layer for the Agent orchestration #129
Unanswered
darielnoel
asked this question in
Roadmap
Replies: 1 comment 1 reply
-
Persistence is required for a stateless implementation, which will be a lot more scalable compared to sessions sticking to specific compute instances. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Refers to #128
Is your feature request related to a problem? Please describe.
Right now, users who want to run their agents have to manage the persistency layer themselves, which can be cumbersome and time-consuming.
Describe the solution you'd like
Implement a persistency layer that allows saving the agent's state in a database, enabling visualization of results across different platforms.
Describe alternatives you've considered
Developing custom solutions or using third-party services, but they lack native integration with KaibanJS.
Additional context
This feature would significantly ease the workload for developers by providing out-of-the-box persistence, enhancing usability and functionality.
Beta Was this translation helpful? Give feedback.
All reactions