StartOrderRes returns at Created — reservation, authorization, and confirmation continue in the background
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Semantic radar needs more MAP space.
Background continuation does not extend the HTTP reply boundary
• mermaid Note over Workflow (positioned right after StartOrderWorkflowRes/StartOrderRes, before ReserveInventoryReq): 'Background continuation does not extend the HTTP reply boundary.' StartOrderRes(Created) at step 11 does not wait for steps 12-21 (inventory reservation, payment authorization, confirmation) to complete.
Reading the flow
• CommerceApi performs mapping reservation and input validation, but doesn't record the event stream. OrderWorkflowSpot replays the stream to restore the aggregate, records OrderStartedEvent, then updates the projection.
• The client repeats GetOrderStateReq with bounded polling to confirm Confirmed or Failed.