graph LR A[Feature Branch] --> B(GitHub/GitLab) B --> CPR Validation C -->|Static Analysis & Apex Tests| D(Scratch Org) D --> E[Integration Sandbox] E --> F[UAT Sandbox] F --> G[Production]
This report provides a reference architecture for implementing DevOps in complex Salesforce environments. It covers source-driven development (SDD), metadata API limitations, environment management strategies, and the architectural evaluation of the modern tooling landscape (Copado, Gearset, Autorabit, Flosum, native Salesforce DevOps Center). Historically, Salesforce encouraged declarative development (clicks not code). This created the "metadata chaos" problem: two administrators modifying the same Profile or Custom Field in different sandboxes would inevitably cause deployment collisions. salesforce devops for architects free pdf
| Environment | Purpose | Refresh Strategy | Data Strategy | | :--- | :--- | :--- | :--- | | | Ephemeral feature testing | On every PR | Sample dataset (100 records) | | Integration (CI) | Merge validation & conflict resolution | Nightly (auto) | Anonymized production subset | | Staging/UAT | Business sign-off & performance | Bi-weekly | Full copy (masked) | | Production | Live customer environment | Never (backup only) | Live data | 4. Tooling Landscape: Build vs. Buy Architects must decide between the Salesforce DevOps Center (native, free, immature) and ISV solutions (costly, robust). graph LR A[Feature Branch] --> B(GitHub/GitLab) B -->
| Feature | DevOps Center (Native) | Copado / Gearset / Autorabit | | :--- | :--- | :--- | | | Basic (GitHub only) | Full (GitLab, Bitbucket, Azure) | | Data Deployment | None | Advanced (lookup mapping, data plans) | | Pre-deploy Tests | Manual | Automated (Apex, Jest, Browser) | | CI/CD Orchestration | Minimal | Full (Jenkins, GitHub Actions integration) | | Governance (Approvals) | Basic | Advanced (4-eye, change windows) | | Cost | Free (with Salesforce license) | 5-20% of license spend | Buy Architects must decide between the Salesforce DevOps
