phowell
/
pocketflow
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

clarify communication

This commit is contained in:
zachary62 2025-01-06 03:46:56 +00:00
parent 2c76cf769f
commit 9c511f50dd
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/communication.md
View File

@ -17,7 +17,9 @@ If you know memory management, think of the **Shared Store** like a **heap** (sh
> **Why not use other communication models like Message Passing?** > **Why not use other communication models like Message Passing?**
> >
> *Message Passing* works fine for simple DAGs, but in nested or cyclic Flows it gets unwieldy. A shared store keeps things straightforward. High-level patterns like *Message Passing* and *Event-Driven Design* can still be layered on top via *Async Queues or Pub/Sub* in a shared store (see [Multi-Agents](./multi_agent.md)). > At a **low-level** between nodes, *Message Passing* works fine for simple DAGs, but in nested or cyclic Flows it gets unwieldy. A shared store keeps things straightforward.
>
> That said, **high-level** patterns like *Message Passing* and *Event-Driven Design* can still be layered on top via *Async Queues or Pub/Sub* in a shared store (see [Multi-Agents](./multi_agent.md)).
{: .note } {: .note }
--- ---