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

Extending automation with Java and Salesforce Functions

So far Heroku has been used to build web and API experiences coded in Node.js and Postgres and run your code constantly through the use of Heroku Dynos. The interactions with those experiences come from external integrations, typically where response times are important. Salesforce Functions, however, offers much of the flexibility of Heroku Dynos with respect to support for additional programming languages, such as Java, Node.js, and Python as well as offering greater elastic scale for more intensive workloads that require more memory, CPU, and asynchronous scale compared to Apex. Functions also have no callout or asynchronous limits when compared to Apex.

In contrast to Heroku Dynos, Salesforce Functions run only when needed, so only use up compute resources when needed; a downside of this is there can sometimes be a startup cost if a function has not been invoked recently. One big difference is that they have tighter integration...