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

Clicks and code

Before we start looking at architectural patterns and solutions to these problems, we should discuss the proverbial elephant in the room: clicks and code or clicks versus code. One of the most powerful features of the Salesforce platform is the fact that there is a wealth of low or no-code tools that can be used to get a solution up and running in a relatively short amount of time. These tools stretch from formula fields through to powerful point and click tools such as flow.

Firstly, I would like to advocate that when building using click-based tools, a number of best practices are followed that will make these solutions more scalable and manageable over time. Most importantly, we should follow these two best practices:

  • Use a single Process Builder process per object
  • Implement bulk patterns within Flow

Process Builder processes do not have a defined order of execution; that is, if you have two processes defined per object, then you cannot guarantee...