Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Salesforce Platform Enterprise Architecture- fourth edition
  • Table Of Contents Toc
  • Feedback & Rating feedback
Salesforce Platform Enterprise Architecture- fourth edition

Salesforce Platform Enterprise Architecture- fourth edition

By : Andrew Fawcett
4.7 (39)
close
close
Salesforce Platform Enterprise Architecture- fourth edition

Salesforce Platform Enterprise Architecture- fourth edition

4.7 (39)
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)
close
close
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

Extending application logic with Apex interfaces

An Apex interface can be used to describe a point in your application logic where custom code written by Developer X can be called. For example, in order to provide an alternative means to calculate championship points as driven by Developer X, we might expose a global interface describing an application callout that looks like this:

global class ContestantService {
   global interface IAwardChampionshipPoints { 
    void calculate(List<Contestant__c> contestants) ; 
  } 
} 

If you are not using a managed package to distribute your application, you do not need to use the global modifier as shown above. Since, in the case of unmanaged packages, everything contained within them is by default visible (including source code) to the org that has the package installed.

By querying Custom Metadata records from the Callouts Custom Metadata type, which has been included in the source code for this chapter, the...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY