vichayturen commented on issue #183:
URL: 
https://github.com/apache/incubator-hugegraph-ai/issues/183#issuecomment-2692091406

   Currently, I've only reviewed the workflow aspects of `llamaindex` and 
`crewai`. Both tools exhibit similar performance and syntax for building 
workflows. In terms of usage, they follow an event-driven model and support 
asynchronous task construction. Based on their coding characteristics, my 
conclusions are:  
   - `llamaindex` offers higher flexibility but results in more disorganized 
code.  
   - `crewai` has a cleaner design but more limited functionality.  
   
   The **Graph Rag** workflow in `incubator-hugegraph-llm` combines the 
**text2gql** and **subgraph query** approaches. The workflow-building 
capabilities of the two aforementioned tools can cover the current logic, so I 
lean toward `crewai` for its more streamlined workflow implementation. 
Additionally, in my view: The immediate benefit of introducing **Agent** and 
**Task** concepts is to better manage prompt templates, so adopting these 
should primarily consider performance and dependency management.  
   
   Next steps:  
   1. Integrate these concepts to build a fully fixed Graph Rag workflow with 
API access.  
   2. Strategic priorities: Should the focus be on improving flexibility or 
enhancing the existing Graph Rag workflow?  
      - If prioritizing flexibility: Should the goal be to  
        a) simplify creating new workflows,  
        b) ease adjustments to workflow composition/sequence, or  
        c) enable easy overrides of individual flow implementations?  
   These questions require further consideration.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to