Hybrid

Real systems usually combine fan-out, fan-in, and pipeline stages rather than using one pattern in isolation.

Why we need this / what value this brings

Real-world flows rarely fit one pure pattern — recognizing the combination helps you apply the right failure-handling at each sub-part instead of one blanket strategy for the whole flow.

When to use this

Whenever a flow is complex enough that describing it as a single pattern feels forced.

How to use or implement this

Decompose the flow into its constituent stages/branches, name each sub-part's pattern, and reason about failure/retry per sub-part rather than for the whole flow at once.

Research questions

• Map a real Localz flow (e.g. booking creation) and see how many of these patterns it actually combines end to end.

---

Empty folder — drop notes, links, and findings here as you research.