View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Architecture arc42 |  Growth Golden Circle |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | In positioning and communication, what an offering actually stands for often becomes blurred. The Golden Circle sharpens a product's inner rationale and connects purpose, approach, and offering into a clear statement. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 1-2 Tage | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 1-4 | 1-8 | 3-20 Reviewer |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View | Why Statement, Messaging Notes, Positioning Draft | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication | MarketingPositioningCommunication | ArchitectureDecisionAsyncGovernance |