A static example Why was order submission designed as asynchronous?
This answer comes from the current ecommerce sample model, reviewed on 2 November 2026. It describes recorded design intent, not a measured performance result.
- Question and scope: the Orders model, specifically the rationale for
orders.CMD001 - Submit Order. - Recorded decision:
orders.DC001 - Use async command for order submission - chooses an asynchronous command to avoid blocking the user while payment and inventory checks complete. - Linked goal:
orders.GL001 - Process orders within 2 seconds - is the motivation recorded on the decision. This is a goal, not a benchmark. - Answer and limit: the decision records responsiveness and independent scaling as its rationale, with eventual consistency as a tradeoff.
orders.FN001 - A draft-then-submit stage survives in three operations and a lifecycle that no longer has it - records a discrepancy: the running shop has no submit route. The design still needs reconciliation.
Read the smaller public ecommerce reference example (v2.6). The answer above uses the current v2.8 sample; these versions are different. Sources: the Orders decision record, motivation, command definition and implementation finding. The public example may advance separately.
The supported entity lookup returns the decision's rationale and typed links to its goal and command. The list above is an editorial summary of those lookups, not an interactive demo or evidence that the shop implements the decision.