Architecture in practice

Event-driven commerce

Trace an order from the API to a topic and fulfilment worker.

This opens a separate browser draft; your main draft remains unchanged.

Readable source

The labels explain the system to a reader. Stable identifiers connect the nodes to the flows. Keep a copy of this source, then adjust it to match your own architecture.

# Event-driven commerce
- Orders API {#api type=service x=80 y=100}
- orders.v1 {#orders type=topic x=400 y=100}
- Fulfilment {#worker type=service x=720 y=100}
## Flows
- api -> orders {#publish label="order accepted"}
- orders -> worker {#consume label="fulfil order"}

Make one useful change.

Rename a component, explain a connection or add a note about a missing assumption. Export the result as Markdown, JSON or YAML to keep an editable copy.

Learn the import and export workflow