Adopt a workflow manager instead of develop one #6570
dmvieira
started this conversation in
Feature suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First, thank you for this amazing framework! I've been using it in production applications and noticed that Autogen's current features are quite basic compared to what other open-source projects have developed over many years.
For instance, a workflow manager like Prefect, Dagster, or Luigi could provide resilient, step-by-step execution (or agent-by-agent execution, adapting for Autogen). Autogen, however, seems to be developing its own Graphflow from scratch for this purpose.
Another challenge these workflow managers address is runtime execution. They can run flows in various environments: parallel, sequential, within Docker, or across clusters. Currently, Autogen only offers a simple single-threaded runtime. I understand Autogen is developing a gRPC-based communication protocol, which will also require a more robust runtime.
These workflow managers could even serve as a pattern for multiple agent teams collaborating. You can find an extended list of such managers. This list includes projects like Ray, which excel at runtime management but also offer workflow features.
I'm not sure if this is best categorized as a discussion or a feature request, so feel free to categorize it as you see fit!
Beta Was this translation helpful? Give feedback.
All reactions