Flow Diagrams
How data moves through Ironflow — from event emission to execution, cancellation, and real-time notifications.
| Diagram | Description |
|---|---|
| NATS Streams | 5 JetStream streams, KV buckets, DB vs NATS ownership |
| Emit Flow | Async trigger, and every consumer one event reaches |
| EmitSync Flow | Synchronous trigger: subscribe to RESULTS, wait for every matched run |
| Event Ingest Flow | External NATS → EventRouter → the same dispatch pipeline |
| PubSub Flow | Real-time notifications via the PUBSUB stream |
| Entity Stream Flow | Append-only events, optimistic concurrency, two outbox rows |
| Cancel Flow | Run cancellation: DB commit first, CANCEL stream second |
Emit Flow and Entity Stream Flow share one fan-out diagram, because they differ only by what they add: emit() writes one outbox row, append() writes two plus a best-effort stream frame. Both also point at Request Lifecycle and Event Sourcing Flow for the paths those diagrams already draw in full.