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 | ![]() Engineering Golden Path | ![]() Domain Modeling Context Map | ![]() Domain Modeling Domain Context Map |
|---|---|---|---|---|
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. | When teams need a reliable default path for frequent use, sprawl quickly emerges without any guiding logic. Golden Path bundles the preferred path so good practice becomes easy and deviation becomes deliberate. | 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. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 1-3 Tage Setup, laufend | 1-3 h | 1-3 h |
Participantsdifferent | 1-3 | 2-8 | 2-8 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Golden Path Guide, Templates, Quality Checks | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | EngineeringProductivityGovernance | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries |



