An architecture decision is a software design choice that evaluates:
- a functional requirement (features).
- a non-functional requirement (technologies, methodologies, libraries).
The purpose is to understand the reasons behind the current architecture, so they can be carried-on or re-visited in the future.
A black and white comic book illustration of a female superhero on the Moon. She is using her laser vision to carve the letter L on the moon surface. Behind her, the dark sky is filled with stars and the Earth is visible. The Moon’s surface is rough and rocky, with many craters and shadows. On the Moon's surface, we can some natural stacks of crystals and diamonds that are sparkling.
- Created: May 2023
The workflow with the different phases of engraving
- Simplicity
- Flexibility
A semi-flexible workflow in which some steps are expected (ex: validation) while some other are more flexible (ex: action)
sequenceDiagram
participant V as Validation
participant S as Shield
participant A as Actions
participant F as onFinish
V->>S: Check opts, headers, parameters, payload, context
S->>A: Check opts, headers, parameters, payload, context
A->>F: Store record to latest and historical storage
F->>+A: Notify that the record has changed