You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[**Parallel Execution**](parallel.md) - Master broadcasting and spreading
185
+
-[**Parallel Execution**](parallel.md) - Master broadcasting and mapping
186
186
187
187
## Comparison with Original API
188
188
189
189
The original graph API (documented in the [main graph page](../../graph.md)) uses a class-based approach with [`BaseNode`][pydantic_graph.nodes.BaseNode] subclasses. The beta API uses a builder pattern with decorated functions, which provides:
190
190
191
191
**Advantages:**
192
192
- More concise syntax for simple workflows
193
-
- Explicit control over parallelism with spread/broadcast
193
+
- Explicit control over parallelism with map/broadcast
194
194
- Built-in reducers for common aggregation patterns
Copy file name to clipboardExpand all lines: docs/graph/beta/joins.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Join nodes synchronize and aggregate data from parallel execution paths. They us
4
4
5
5
## Overview
6
6
7
-
When you use [parallel execution](parallel.md) (broadcasting or spreading), you often need to collect and combine the results. Join nodes serve this purpose by:
7
+
When you use [parallel execution](parallel.md) (broadcasting or mapping), you often need to collect and combine the results. Join nodes serve this purpose by:
8
8
9
9
1. Waiting for all parallel tasks to complete
10
10
2. Aggregating their outputs using a [`Reducer`][pydantic_graph.beta.join.Reducer]
0 commit comments