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

Chapter 3: Triggers and Managing Trigger Execution

In this chapter, I want to discuss Apex triggers and correctly managing and developing a structured execution framework for using triggers within Apex.

Triggers are where most developers start working in Apex on the Salesforce platform, and I would personally estimate that's where the majority of Apex bugs are found. I think there are a few reasons for this:

  • Triggers demand bulkification, and a small resource leak can easily break a Governor Limit.
  • Triggers often fire off other save processes that themselves may fail or over-consume resources.
  • Triggers can be impacted by administrative changes more than other areas of code (validation, processes, flows, and so on).
  • Where the triggers are the first thing many developers touch, they are the most prone to bugs due to inexperience.

In this chapter, we will cover the following topics:

  • How triggers operate
  • The Salesforce save order of execution...