Key facts
- The gallery shows orchestration patterns as graph shapes rather than as product brands.
- Each pattern includes a compact pseudocode sketch that can be adapted to a tiny runtime or a heavier framework.
- The same concepts recur: named nodes, explicit actions, shared state, and a clear stop condition.
Clickable gallery
Choose a graph shape
Pseudocode
Pattern selection is a design decision
The same product can move between these patterns over time. A support workflow may begin as a fixed chain, grow a decision node for tool choice, add RAG for policy context, then use map-reduce for large account histories. The important move is to make each transition explicit.
If a pattern feels unclear, return to the state contract. Name what each node reads, what it writes, and which actions it can return. That vocabulary matters more than the runtime brand.
FAQ
Are these patterns tied to Pocket Flow?
No. The shapes are generic orchestration patterns. You can implement them in a tiny runtime, LangGraph, LangChain, LlamaIndex workflows, or another system.
Why show pseudocode instead of framework code?
Pseudocode keeps the control flow visible. After the graph is clear, you can translate it into the runtime your project actually uses.
Which pattern should I start with?
Start with workflow when the order is known, agent loop when the model chooses actions, RAG when external knowledge matters, and map-reduce when work splits naturally.
Cite this page
Orchestration pattern gallery. PocketFlow AI Guide. Updated July 6, 2026. https://pocketflowai.com/tools/pattern-gallery/
PocketFlow AI Guide. "Orchestration pattern gallery." Accessed July 6, 2026. https://pocketflowai.com/tools/pattern-gallery/