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

Measure twice, cut once

In order for us to begin understanding how we can improve our application's performance, we must first know how it is performing and what resources are being utilized by the application. This can be summed up in the following quote:

If you cannot measure it, you cannot improve it

This quote is attributed to many individuals (Lord Kelvin and Peter Drucker, to name two), but regardless of who said it, it captures the essence of how we should think about performance testing and analysis. Before we can make any reasonable assertion that we want to improve the performance of some code, we need to measure and understand what the code is doing and how resources are being utilized. Without this measurement step, we will have no true understanding of whether the work we have undertaken has improved the performance of our code or whether it has had no significant impact at all.

I have titled this section Measure twice, cut once, as this is another important...