ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #apex
How Database.Batchable splits million-record jobs into governor-limit-isolated chunks: the start/execute/finish contract, QueryLocator vs Iterable, batch sizing, and partial-failure handling with a worked example.
Queueable Apex is the underused middle ground between @future and Batch Apex: complex arguments, fresh governor limits, and job chaining — with one sharp fan-out limitation to design around.
Step‑by‑step guide to diagnose and fix Apex CPU time limit exceeded errors in Salesforce, with checks, fixes, and escalation rules.
When an async Apex job fails, the caller often needs a reliable way to react. Salesforce's Transaction Finalizer attaches a post-execution handler to a Queueable job. This note covers requirements, minimal design, trust boundaries, operational checks, failure modes, and redesign triggers.
Hardcoded constants and Custom Settings both fail as Apex configuration. Custom Metadata Types deploy like code, query for free against governor limits, and let admins change behavior without a release.
How to declare and read configuration in Salesforce using Custom Metadata Types, accessed in Apex without SOQL queries, plus limits and pitfalls to avoid.
Learn how to implement the Cache-Aside pattern using Apex Platform Cache to reduce SOQL query counts and optimize performance in high-volume Salesforce environments.
Learn why a naive Apex trigger that updates a parent record for each child can hit SOQL limits, and how to rewrite it using bulk‑safe patterns that stay within governor limits.
If you’ve hit the @future limits or need to pass complex data, Apex Queueable offers a supported, flexible alternative. This post walks through why, how, and when to use Queueable jobs, with a concrete example and trade‑offs.
salesforce