Book Image

Salesforce Platform Enterprise Architecture - Fourth Edition

By : Andrew Fawcett
Book Image

Salesforce Platform Enterprise Architecture - Fourth Edition

By: Andrew Fawcett

Overview of this book

Salesforce makes architecting enterprise grade applications easy and secure – but you'll need guidance to leverage its full capabilities and deliver top-notch products for your customers. This fourth edition brings practical guidance to the table, taking you on a journey through building and shipping enterprise-grade apps. This guide will teach you advanced application architectural design patterns such as separation of concerns, unit testing, and dependency injection. You'll also get to grips with Apex and fflib, create scalable services with Java, Node.js, and other languages using Salesforce Functions and Heroku, and find new ways to test Lightning UIs. These key topics, alongside a new chapter on exploring asynchronous processing features, are unique to this edition. You'll also benefit from an extensive case study based on how the Salesforce Platform delivers solutions. By the end of this Salesforce book, whether you are looking to publish the next amazing application on AppExchange or build packaged applications for your organization, you will be prepared with the latest innovations on the platform.
Table of Contents (23 chapters)
1
Part I: Key Concepts for Application Development
6
Part II: Backend Logic Patterns
11
Part III: Developing the Frontend
14
Part IV: Extending, Scaling, and Testing an Application
21
Other Books You May Enjoy
22
Index

Where is Apex used?

As we have discovered, Apex code can run at any time for a variety of reasons, both in the foreground and background, and governor limits vary accordingly. You can read more about this in Apex Transactions and Governor Limits, from the Apex Developer Guide.

Occasionally, if you have some Apex code that is acting as a library of commonly used code, this code may need to act intelligently depending on the context it’s running in. For example, HTTP callouts are not allowed in Apex Triggers but are in almost all other cases. In order to avoid errors and take mitigating action, code can reference the Quiddity enumeration. The following code can be used to obtain the current enumeration for the request currently being executed.

Quiddity currentType = Request.getCurrent().getQuiddity(); 

The following table lists the types of execution contexts that Apex code can be run from, their Quiddity enumeration value, and considerations with respect to security...