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

The OODA methodology

The OODA (short for Observe, Orient, Decide, Act) loop and OODA methodology was first coined by US military strategist Colonel John Boyd and was applied to help make improved decisions during combat operations. It has since become widely used within different industries and operations, and I have found it to be an extremely effective way of working with performance testing, although it has been used within software circles by a variety of individuals for a long time.

The OODA loop comprises four steps, which form its acronym. These steps are shown in the following diagram:

Figure 14.1 – The OODA loop

We can use this same loop to define a methodology that will allow us to test the performance of our applications and determine whether to take action. Let's look at these steps in more detail and how they specifically relate to the process of performance analysis.

Observe

In this first step, we take our measurements for...