"Architectural Decisions" to strengthen "Architecturally Significant"

adr / madr

Markdown Architectural Decision Records

https://adr.github.io/madr/

Other

1.38k stars 394 forks source link

"Architectural Decisions" to strengthen "Architecturally Significant" #134

Open koppor opened 1 month ago

koppor commented 1 month ago

Short: We think to revert https://github.com/adr/madr/issues/41 to strengthen "Architecturally Significant".

"Any": Too broad
"Architectural": Maybe too narrow?

Is going back to "Markdown Architectural Decision Records" a good idea?

koppor commented 1 month ago

Note: spotify backstage uses docs/architecture-decisions as path.

jonthenerd commented 3 weeks ago

For what it's worth, I think it's relevant to keep MADR related to architecture. Architecture implies significance. Going through the labor of establishing a decision record is really only warranted when that decision will have a significant impact. Hence, why you wouldn't do it for "any" decision. While you could you probably shouldn't and most wouldn't.