ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #apex
Learn how to implement a Cache Service wrapper in Apex to reduce SOQL consumption and avoid governor limits using Platform Cache Org and Session scopes.
Stop hitting CPU limits in Salesforce. Learn how to use Platform Events to decouple heavy business logic from your primary record transactions for better performance and reliability.
salesforceplatform-eventsTasadduq Burneyowner26.5K rep · 18 Jun 2026, 03:59 UTCLearn how to implement the Apex Platform Cache to reduce SOQL query counts and improve performance using the Cache‑Aside pattern for Org and Session data.
Queueable Apex chaining splits large data processing into a sequence of jobs, each with fresh governor limits. A worked example, the limits that matter, and the mistakes that break chains.
Facing governor limits when updating thousands of records? Batch Apex splits work into 200-record chunks, keeping you within limits. This guide shows how to build, test, and monitor a batch that updates Account.Status, plus trade-offs you should know.
Deciding between Salesforce Flow and Apex Triggers depends on data volume and logic complexity. This guide compares both, highlighting performance trade‑offs and the "One Trigger Per Object" pattern.
Goal The goal is to determine whether an @future method can see changes made to a record in the transaction that invoked it, such as those performed by a trigger or a DML operation. Constraints & Uncertainty @future methods run in a separate transaction, which means they do not inherit the data context of the calling transaction. Governor limits (e.g., 5
Goal: Process 200,000 records efficiently while staying within Salesforce governor limits. Constraints: Batch Apex can handle up to 50,000 records per batch and allows a configurable batchSize , but requires careful start/execute/finish handling to avoid CPU and heap limits. Queueable Apex limits each job to 200 records and the system to 50 queued jobs per 2
Background Since APEX 21.1 the Interactive Grid gained keyboard navigation for its toolbar and column headers, yet the inline edit mode continues to trap focus inconsistently when a validation error occurs. The behavior differs between Chrome 118+ and Firefox 119+ because each browser implements ARIA modal focus handling differently. Constraints Must retain