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

Lightning architecture

In this section, we will discuss key layers of the Lightning architecture, which will allow you to have a better framework of understanding as we go deeper.

A key aspect that took me by surprise at first was the need to write client-side controllers in JavaScript. This can be particularly puzzling at first if you are a Visualforce developer, but it is a vital part of being a Lightning developer and is a reflection of its client-side architecture. As we saw in the previous chapter, Apex server-side controllers still play a part but are mainly used for accessing your backend Apex Services and Selectors.

In general, Lightning development is much more componentized. In terms of how the UI is designed and how the code is factored, the two are much more aligned, making it easier to maintain and navigate code. This also gives a much greater emphasis on the separation of concerns within the UI tier.