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

Exposing endpoints

In the previous section, we saw how our new custom API was exposed at the endpoint /services/apexrest/hospital. The starting portion of this URL will be the instance for our Salesforce org, for example, https://um1.salesforce.com. Our endpoints are therefore accessible through the standard API authentication mechanisms—that is, using OAuth 2.0 or by passing sessionId into the request.

Accessing Salesforce APIs in this manner is covered in detail in the REST API Developers Guide and details how we can access APIs using the standard mechanisms. What about the instances where we want to expose an API to the public for use?

Note

In general, we will want our APIs to be authenticated to allow us to ensure that we are controlling the flow of information and keeping data private. There are some instances, however, where we will want to expose data to the public for it to be used. As an example, one organization I worked with maintained a public database...