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

We began this chapter by understanding the mindset we should have when profiling performance in our applications to make decisions, that of measure twice, cut once, to ensure that we had sufficient data before we acted. From this we looked into a structured methodology, OODA, to help us make informed decisions in profiling and understanding the performance of our Apex code.

We looked at the four steps of OODA individually and how they fit into a broader whole to help us profile, analyze, decide, and act on our code as part of a performance analysis system. From this, we looked into more details of how we perform the analysis required in the orient phase using big O notation and magnitude analysis. Although this involved some basic algebra and mathematics, it provided us with a simple way of reviewing and understanding how to quantify and communicate the impact of the specific processes we had implemented.

ith this tool available to us, we saw specifically how we can...