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

In this chapter, we began by discussing the lifecycle of a request for a Salesforce application and how that is impacted by the Apex code we write. We saw how important it is for developers to remember that any code we write in Apex that is run on the server may block the user's application from being responsive and create a negative user experience. From this, we discussed, when looking at how we determine how to improve performance, that we must understand the structure of the Salesforce platform and what that means in terms of resource management—namely that resources are shared and that a baseline of performance must be guaranteed by having a limit to the resources that a single operation can use.

These limits are the governor limits, and we saw how they provide a guaranteed level of performance for end users across the platform. We also discussed why we as developers should embrace the governor limits to help us ensure that our application will avoid producing...