sf-apex-enterprise-patterns

What problem does it solve?

Centralizes SOQL, separates business logic, and enforces atomic DML boundaries to reduce duplicated trigger logic, improve testability, and make growing Apex codebases maintainable as teams and class counts increase.

Core Features & Use Cases

• Selector Layer: Centralize queries for each object to remove ad-hoc SOQL from business logic.
• Domain Layer: Encapsulate record-level business rules and trigger behavior for easier testing and reuse.
• Service & Unit of Work: Orchestrate cross-object processes, own transaction boundaries, and commit DML atomically using a Unit of Work pattern; supports either FFLIB or lightweight implementations.
• Use Case: Migrate complex trigger logic into Domain classes and implement Services that coordinate Create/Update operations across Account and Opportunity records with a single atomic commit.

Quick Start

Use the sf-apex-enterprise-patterns guidance to review your Salesforce codebase and recommend Selector, Domain, Service, and Unit of Work structure for Accounts and Opportunities.