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 Request for Comments |  Domain Modeling Context Map |  Architecture arc42 |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-2 Tage | 1-3 h |
Participantsdifferent | 3-20 Reviewer | 2-8 | 1-4 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Map, Integration Patterns, Boundary Notes | Architecture Document, Context View, Runtime View, Deployment View | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Domain-Driven DesignBoundariesStrategy | ArchitectureDocumentationCommunication | Domain-Driven DesignBoundariesModeling |