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

An overview of REST

REST stands for REpresentational State Transfer and is an architectural structure designed to make it simple to connect systems across the internet using existing standards and protocols. The purpose of REST is to help define a uniform set of stateless operations that can be performed between systems. A basic driving principle behind a RESTful API is that it should use the standards that form the basis of the internet, that is, the HyperText Transfer Protocol (HTTP), to allow for resources to be accessed and data transferred between systems in a simple and repeatable manner.

In general, RESTful APIs require a descriptive Uniform Resource Locator (URL) to identify the resource we are working with, a standard HTTP method to indicate what action is being performed, and a media type description to describe the format of the data being transferred or the required format for data being returned.

Ideally, the URI for a RESTful API is a clean URL, or user-friendly...