PMPhushya Mithra Gauriinphushyamithra.hashnode.dev00Queueable Apex: The Modern Choice2d ago · 5 min read · If you've read the article about @future, you know @future gets the job done. But Salesforce itself recommends moving away from it — and Queueable Apex is the reason why. Queueable has everything @futJoin discussion
PMPhushya Mithra Gauriinphushyamithra.hashnode.dev00Scheduled Apex: The Alarm Clock Apr 29 · 5 min read · Batch Apex handles volume. @future handles one-off background operations. Queueable handles chaining. But none of them answer one question — when? Scheduled Apex is the answer. It's how you tell SalesJoin discussion
PMPhushya Mithra Gauriinphushyamithra.hashnode.dev00@future: The Quick Fix — Async Apex Apr 28 · 5 min read · Sometimes you don't have 50,000 records. You just have one operation that can't run right now — either because of where it's being called from, or because it needs to reach out to an external system. Join discussion
PMPhushya Mithra Gauriinphushyamithra.hashnode.dev00Batch Apex: One Brick at a Time — Async Apex Part 2Apr 26 · 5 min read · In Part 1 we talked about why Async Apex exists — multi-tenancy, Governor Limits, and why going async gets you significantly more room to work. Now let's get into the first tool that actually uses it.Join discussion
PMPhushya Mithra Gauriinphushyamithra.hashnode.dev00Asynchronous Apex: The 2AM Laundry RuleApr 25 · 3 min read · If you've spent any time writing Apex, you've probably run into a wall — your logic is correct, your tests pass locally in your head, and then Salesforce throws a LimitException at you like you did soJoin discussion
