Trailblazer Community
Feed

Getting Started

  • What is Trailhead
  • myTrailhead
  • Trailblazer Community
  • Career Growth

Learn

  • Trails
  • Trailmixes
  • Modules
  • Projects

Credentials

  • Superbadges
  • Certifications
  • Maintain Certifications

Salesforce

  • Salesforce.com
  • AppExchange
  • Developers
  • Help Portal
© 2026 Salesforce, Inc. All rights reserved. Privacy Terms of Use Trust Accessibility Cookie Preferences
  1. Feed
  2. Post
EO
Emeka Okonkwo
Salesforce Administrator · May 14, 2026 2:45 PM
Asked in #Apex

Apex bulkification — is the "one trigger per object" rule still load-bearing in 2026?

Half the codebase I inherited follows the classic single-trigger-per-object rule with a dispatcher class. The other half uses a per-feature trigger handler pattern (FeatureAHandler, FeatureBHandler) wired up through a framework.

For greenfield orgs, is anyone genuinely defending single-trigger anymore? It feels like cargo cult at this point — the original reason was order-of-execution predictability, and the modern handler frameworks solve that explicitly.

Discuss this in Slack for faster answers and real-time help.

41 replies · preview from Slack

Active in Slack

Conversation lives in #apex. Open Slack to post, reply, and react.

About the asker

EO
Emeka Okonkwo
Salesforce Administrator
Adventurer

Related learning

  • Trail
    Build an Agentforce Sales Agent
  • Badge
    Agent Handoff Patterns
  • Trail
    Omni-Channel Routing Foundations

Related threads

  • Best pattern for handing off from Agentforce to a human agent mid-conversation?
    14 replies
  • How are you grounding Agentforce responses without leaking PII into the prompt?
    19 replies
  • Identity resolution rulesets — when to use deterministic vs. probabilistic?
    27 replies