From 32c7b9707b3f2efa4ddfa250832e4ed4dac4be84 Mon Sep 17 00:00:00 2001 From: zachary62 Date: Mon, 6 Jan 2025 03:50:39 +0000 Subject: [PATCH] clarify communication --- docs/communication.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/communication.md b/docs/communication.md index 5830019..bbb0648 100644 --- a/docs/communication.md +++ b/docs/communication.md @@ -17,9 +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?** > -> 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. +> 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)). +> That said, *high-level* multi-agent 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 } ---