Conventional web approach — delivery/dispatch comparison
queue · registry · timeout job · event bus (orange) attach as separate components
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.
Coordination overhead attached (orange)
• The queue, registry, timeout job, and event bus are separate components. DeliveryDispatch does not remove this responsibility; it shifts the boundary so the DispatchWorker owns offer state and deadlines while the Framework handles Actor routing and session binding.
• Color basis: Session Registry follows the sibling comparison diagram (01-delivery-existing), which places session-affinity overhead like a sticky LB as messagebus (orange) and the L7 LB/gateway as external (gray). Dispatch Worker is retained business logic (→ DispatchWorker), so it is frontend (blue).
Correspondence
• session registry → Courier/Customer Actor and bound session. dispatch queue/worker → DispatchWorker. event bus → status/evidence on Tracking. websocket push gateway → CustomerGateway/CourierSession. timeout job → worker sweeper.