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

Object-oriented programming in Apex

Apex is a fully featured object-oriented programming language that enables developers to utilize features such as inheritance, polymorphism, abstraction, and encapsulation in order to develop applications in a way that is easy to manage, scale, and test. It is often the case that the first introduction to Apex that many developers get is through a trigger, which, by nature, is a very linear structure for organizing code. A trigger will run from the first line to the last in order and does not have any of the standard OOP capabilities; triggers cannot implement an interface or extend any classes. Although it is a best practice to extract the logic within a trigger to a set of classes and methods, as we saw in Chapter 3, Triggers and Managing Trigger Execution, it is not a requirement to do so, and many triggers are still written that do not follow this best practice.

Many developers do not start to work with the object-oriented capabilities of...