Application Integration Patterns for Salesforce Lightning Platform

Evaluate an Integration Pattern

Learning Objectives

In the wake of finishing this unit, you’ll have the option to:

Distinguish an answer related to the Remote Process Invocation—Request and Reply integration pattern.

Clarify the advantages of the Remote Process Invocation—Request and Reply integration pattern.

The Remote Process Invocation—Request and Reply is a typical Salesforce Lightning Platform integration pattern. It’s otherwise called Request and Reply, or Request and Response. In this unit, you figure out how to evaluate the pattern and discretionary answers for the example scenario.

Example Scenario

Envision you use Salesforce to oversee leads, set out open doors, and oversee contacts. Your integration arrangement necessitates that Salesforce incorporates request data, however you utilize an outer framework to deal with your orders. Your integration objective is to associate your outer framework to Salesforce to deal with your orders.

You audit the Request and Reply pattern to figure out which arrangement is ideal to tackle your integration issue.

Remote Process Invocation—Request and Reply

Layer: Business Logic

Timing: Synchronous

Course: Salesforce → System

Volume: Ideal for little exchanges (constant exercises)

The Remote Process Invocation—Request and Reply pattern is ideal for plans that send a solicitation from Salesforce to an outer framework and require a reaction back.

How Does the Remote Process Invocation—Request and Reply Pattern Work?

An occasion started process begins from Salesforce and settles on a decision to an outside framework. The solicitation is set off accordingly by the UI. This incorporates clicking a catch on a page or a Lighting web part (LWC) conjuring an Apex class. The outer framework finishes the solicitation and sends a coordinated reply to Salesforce. The reply is then processed by Salesforce, and Salesforce refreshes the information depending on the situation.