Salesforce ArchitectureIntermediatecoeadrgovernance
Define Salesforce architecture decision record process for CoE governance
Real World Scenario
Teams debate same build-vs-buy questions repeatedly; no record of why org chose MuleSoft over native Integration.
Expected Answer
• ADR template: context decision status consequences alternatives
• CoE repository Git or Confluence linked from integration catalog
• Mandatory ADR for new org integration pattern technology choice
• Review board approves superseded ADR with migration plan
• Onboarding architects read ADR history not repeat debates
• Quarterly ADR health check outdated decisions flagged
• Link ADR to metadata tags Integration_Pattern__mdt
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. ADR template: context decision status consequences alternatives. CoE repository Git or Confluence linked from integration catalog. Pick based on your integration pattern and team capability. ADRs preserve institutional memory—without them every reorg relitigates same decisions. Balance speed of delivery with maintainability.
Architect Perspective
ADRs preserve institutional memory—without them every reorg relitigates same decisions.