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 13: Performance and the Salesforce Governor Limits

In this chapter, we are going to begin our third and final section of the book, where we focus on performance within Apex, how we can profile Apex, and how we can improve the performance of our applications.

Performance as an area of study is something I find fascinating as it contains a number of unique overlaps from both the human and technical sides of software development. Improving performance for the sake of it is likely to lead to code that is much more difficult to maintain and manage going forward. Applications that do not take performance into account will quickly become slow and provide a negative user experience.

For Salesforce applications in particular, code tends to not receive much maintenance after it has been written and deployed, particularly in circumstances where a customer has paid a consultancy to deliver a piece of functionality in a one-off project. I often encounter organizations that contain...