root-at-skic
ebf320a023
- *.archify-decision files: id (unique, words), title, status, date, elements, diagrams, supersedes, and prose; parsed, merged and link-checked in the model index; diagnostics on the file - diagrams point at decisions with decisions: [...] on the diagram, nodes and edges; stripped before Archify, unknown ids reported, completion, hover and go-to-definition for the ids and for elements/diagrams/ supersedes in decision files - Decisions panel on the main.archify page; Decisions rail panel under a diagram (hover lights up the node or connection); decisions on element cards and in the element dialog; decision view for the file, with a lost-model note outside a model - Archify | New Decision… command and template; editor schemas; the three New Model examples carry decisions; docs, changelog, 0.8.0
21 lines
764 B
Plaintext
21 lines
764 B
Plaintext
schema_version: 1
|
|
decision:
|
|
id: queue-between-api-and-worker
|
|
title: A queue between the API and the worker
|
|
status: accepted
|
|
date: 2026-09-16
|
|
elements: [api, queue, worker]
|
|
diagrams: [0200-containers/online-shop.archify]
|
|
context: >
|
|
Order confirmation emails and invoices were sent inside
|
|
the checkout request. A slow mail provider made checkout
|
|
slow; a failing one made checkout fail.
|
|
decision: >
|
|
The API enqueues a job per side effect on SQS. One worker
|
|
service consumes the queue and does the slow work.
|
|
Checkout returns as soon as the order is stored.
|
|
consequences: >
|
|
Emails arrive seconds later, not instantly. Jobs must be
|
|
idempotent because SQS delivers at least once. The worker
|
|
is the second place that writes to the database.
|