Book Image

Mastering Apex Programming

By : Paul Battisson
5 (1)
Book Image

Mastering Apex Programming

5 (1)
By: Paul Battisson

Overview of this book

As applications built on the Salesforce platform are now a key part of many organizations, developers are shifting focus to Apex, Salesforce’s proprietary programming language. As a Salesforce developer, it is important to understand the range of tools at your disposal, how and when to use them, and best practices for working with Apex. Mastering Apex Programming will help you explore the advanced features of Apex programming and guide you in delivering robust solutions that scale. This book starts by taking you through common Apex mistakes, debugging, exception handling, and testing. You'll then discover different asynchronous Apex programming options and develop custom Apex REST web services. The book shows you how to define and utilize Batch Apex, Queueable Apex, and Scheduled Apex using common scenarios before teaching you how to define, publish, and consume platform events and RESTful endpoints with Apex. Finally, you'll learn how to profile and improve the performance of your Apex application, including architecture trade-offs. With code examples used to facilitate discussion throughout, by the end of the book, you'll have developed the skills needed to build robust and scalable applications in Apex.
Table of Contents (21 chapters)
1
Section 1 – Triggers, Testing, and Security
8
Section 2 – Asynchronous Apex and Apex REST
15
Section 3 – Apex Performance

Summary

In this chapter, we took a deep dive into how Apex triggers function and how to improve our triggers through the use of trigger handlers.

We started by discussing the Salesforce save Order of Execution, how it operates, and the side effects that it can have when it is not properly accounted for when it comes to designing and developing solutions. As we discussed, not correctly accounting for the way in which it fires different actions can lead to recursion and overuse of resources, including unintended side effects and governor limit breaches in the most extreme scenarios.

With this knowledge, we reviewed how we should correctly architect our triggers for scalability and built out a basic trigger handler pattern to enable us to manage and maintain our code. This handler met our three criteria and allowed us to separate the execution of the code for our triggers from the actual trigger itself, thus making it easier to maintain and test.

Finally, we looked at how we...