From an architect perspective, when do you choose Apex vs Flow vs declarative tools?

The decision pivots on multiple factors at architect level.

Always declarative when possible:

• Validation rules.
• Field updates.
• Simple workflows.
• Standard reports / dashboards.
• Page layouts / Dynamic Forms.
• Out-of-box features.

Flow when:

• Multi-step orchestration.
• User-facing screens (Screen Flows).
• Conditional logic admins maintain.
• Cross-object writes.
• Scheduled tasks (Scheduled Flows).
• Most automation in modern Salesforce.

Apex when:

• Performance critical — flows hit governor limits faster.
• Bulk operations beyond Flow's reach — millions of records.
• Complex error handling — try/catch, partial-success, custom exceptions.
• Recursion-aware logic — cleaner in Apex with static guards.
• Apex Managed Sharing — flows can't write to __Share tables.
• Custom REST/SOAP endpoints.
• Complex callouts with retries, transformations.
• LWC backing — @AuraEnabled Apex.

Hybrid (often best):

• Flow at the orchestration layer — admins maintain.
• Apex Invocable Methods for heavy lifting.
• Mix gives admin agility without Apex complexity for everything.

Architect-level considerations:

Maintenance cost:

• Flow: admins can maintain, but complex flows are still hard.
• Apex: developers required, more expensive maintenance.
• Mixed: both teams collaborate; can be friction or strength.

Performance:

• Apex generally faster, more predictable.
• Flow has overhead per element; many elements add up.
• Bulk safety in Apex easier to verify.

Testability:

• Apex unit tests required and powerful.
• Flow testing newer, less mature.
• Apex test coverage is enforced (75%); Flow isn't.

Scaling:

• Flow can hit governor limits at unexpected times.
• Apex more controllable at scale.

Talent:

• Admin-rich orgs do better with Flow.
• Dev-rich orgs lean Apex.

Decision framework:

> Ask first: can this be declarative? If yes, do that. > Then: is this a Flow's natural shape (orchestration)? If yes, Flow. > Otherwise: is this performance-critical, complex, or bulk-heavy? Apex. > For most automations: Flow at top + Apex Invocable for hard parts.

Architect role: enforce this through standards, ARB review, code quality checks. Without governance, individual decisions drift toward "build everything in code" or "build everything in flow" depending on team bias.

The senior architect insight: the right balance shifts over time as Salesforce platform evolves. Flow capabilities expand; what required Apex in 2022 may be Flow in 2026. Reassess periodically.