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

Debugging on Salesforce

Debugging on Salesforce is different than debugging on most other platforms, as Apex code can only be run on the Salesforce servers. If you were building an application for deployment on Heroku, for example, you could still develop and test that application locally before deploying it to the cloud. With Apex code, however, there is no way of running the code locally to ensure that it operates as expected before deploying to the Salesforce servers for compilation and execution. This adds additional challenges for developers in terms of productivity and ease of debugging.

Debugging an issue can be a slow and repetitive process as each edit, save, and then execution action of the code takes multiple saves and potentially multiple page interactions to replicate the behavior. As an example, you may have to save the code (with some amendments or extended debugging statements), then navigate to a page within Salesforce to change or create one or more records, then...