You're reading from Salesforce Platform Enterprise Architecture- fourth edition A must-read guide to help you architect and deliver packaged applications for enterprise needs

Product type Paperback

Published in Mar 2023

Publisher Packt

ISBN-13 9781804619773

Length 712 pages

Edition 4th Edition

Languages

Java

Tools

Salesforce

Concepts

Solution Architecture

Author (1):

Andrew Fawcett

View More author details

Table of Contents (23) Chapters

Preface

1. Part I: Key Concepts for Application Development

2. Building and Publishing Your Application FREE CHAPTER

3. Leveraging Platform Features

4. Application Storage

5. Apex Execution and Separation of Concerns

6. Part II: Backend Logic Patterns

7. Application Service Layer

8. Application Domain Layer

9. Application Selector Layer

10. Additional Languages, Compute, and Data Services

11. Part III: Developing the Frontend

12. Building User Interfaces

13. User Interfaces and the Lightning Component Framework

14. Part IV: Extending, Scaling, and Testing an Application

15. Providing Integration and Extensibility

16. Asynchronous Processing and Big Data Volumes

17. Unit Testing

18. Source Control and Continuous Integration

19. Integrating with External Services

20. Adding AI with Einstein

21. Other Books You May Enjoy

22. Index

Application integration APIs

Having now discussed ways in which the platform exposes standard APIs to your application and its data, this section describes ways in which you can expose the business logic functionality that is encapsulated within your application’s Service layer. First, we will cover ways in which you can build and expose an Apex API for use by Developer X when they are also using Apex, and then we will discuss exposing application APIs for REST for cases when Developer X is using languages other than Apex.

In some cases, Developer X can achieve such functionality through the standard Salesforce APIs. However, depending on the requirements, it might be easier and safer to call an API that exposes existing business logic within an application. You can decide to do this for the same reason you would create a custom UI rather than expect the end users to solely utilize the standard UI (because using your objects directly requires them to understand the...