Application Integration Patterns for Salesforce Lightning Platform

Practice the Layer Approach

Learning Objectives 

• In the wake of finishing this unit, you’ll have the option to:
• Identify the three layers you use to assess integration patterns.
• Depict the two kinds of timing and why they’re significant.

The Layer Approach

Contingent upon your integration activity, you’ll follow various approaches to assess patterns. In this module, you learn how to utilize the layered approach to assess patterns for an application integration activity. Application integration activities are basic integrations for the Salesforce Lightning Platform.

Explore the Four Dimensions

In the layered approach, you utilize the accompanying four measurements to assess integration patterns and arrangements. Each measurement addresses standards that assist you with understanding which arrangement best takes care of your integration issue. Survey each measurement and look at the outcomes against your integration necessities.

Layers: The various sorts of assignments in a framework

Volume: The measure of data synchronized and the change action between frameworks

Timing: Communication timing is either nonconcurrent or simultaneous, where data streams between frameworks continuously (or quickly) or are clumped up for later conveyance

Bearing: The source course, which can be from Salesforce to another framework, from another framework to Salesforce, or bidirectional

Explore the Different Layers

The layered approach separates the application design ideas into coherent classifications. Each layer addresses a division of undertakings in the framework. The most widely recognized approach to partition the assignments is into the accompanying three layers.

• User interface layer
• Business measure layer
• Data layer

This division of assignments assists you with gathering comparable patterns and arrangements. Despite the fact that these layers are independent, they actually speak with one another.

User Interface Layer

The UI layer centers around user cooperations with the framework. In this layer, you identify the segments to coordinate outsider web applications into Salesforce. You join the UI from numerous frameworks, for example, showing Salesforce UI in an outsider application. The UI layer interfaces with the business interaction layer.

• Salesforce material
• Mashups or Lightning out

Business Process Layer

The business cycle layer collaborates with the data and expands on the UI layer. The business rationale incorporates data association, approval, and handling of data exchanges. These exchanges are ongoing calls from the UI or data catch occasions to the database that stores the data.

Here are some model integration arrangements related to this layer.

• Mulesoft Anypoint Platform
• Stage occasions transport (counting Streaming API)
• Streams
• Outbound informing

Data Layer

The data layer is associated with the UI layer and the business cycle layer. It maps and recognizes the essential data source and associations with different fragments of the framework. Data changes, relocation, and replications frequently happen in this layer. The connectors and administrations adjusted to this layer center around data correctness and uprightness as the data penetrates through the arrangement.

Here are some model integration arrangements related to this layer.

• Heroku Connect
• Salesforce Connect
• Pinnacle
• REST and SOAP API
• Composite API
• Mass API

A) Which three layers are the common way to divide tasks in the application architecture?

Show Answers