- *.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
720 B
Plaintext
21 lines
720 B
Plaintext
schema_version: 1
|
|
decision:
|
|
id: opensearch-for-product-search
|
|
title: OpenSearch for product search
|
|
status: proposed
|
|
date: 2026-10-19
|
|
elements: [api, worker, db]
|
|
diagrams: [0200-containers/online-shop.archify]
|
|
context: >
|
|
Catalogue search runs as SQL LIKE queries on the
|
|
database. Typos find nothing and the catalogue page is
|
|
the slowest page in the shop.
|
|
decision: >
|
|
Add a dedicated search service on OpenSearch. The API
|
|
queries it; the worker rebuilds the index from the
|
|
database after every catalogue change.
|
|
consequences: >
|
|
The index is derived data under decision 0001 and may be
|
|
rebuilt at any time. One more service to run. Search
|
|
results can lag the database by the rebuild interval.
|