Can you explain why it is called a graph?

[ravenrip]

I'm coming from a graph database perspective and I don't understand why this is called a graph. I am going to be responsible for explaining this library to my team and I'm struggling out of the gate.
Wouldn't it be better to call it langflow? I have watched a few videos on langgraph and it is described as a flow, not a graph (also it would git rid of the double-g in the name).
Although the term 'node' is used, I don't see how a graph moves a 'chain' into a 'flow' without also using the term 'relationship'.

Any help would be greatly appreciated.

[hinthornw]

@ravenrip LangGraph's StateGraph abstraction extends our implementation of Pregel, the graph processing framework.

The orchestration is organized into nodes (vertices) and edges. Each node performs computation, and the edges determine the control flow. Edges then denote relationships.

[ravenrip]

Thank you. That helps differentiate between graph databases and graph process frameworks.