Application Integration Patterns for Salesforce Lightning Platform -Practice the Layer Approach
Volume centers around the measure of the data and the size of the message imparted. Each Salesforce organization has hard lead representative cutoff points and designations forced. A few distributions, for example, API calls, are extendable by buying extra licenses. The hard drawn lead representative lines, for example, the number of records refreshed through a DML articulation, can’t be broadened. The best practice is to utilize just fundamental advances, connectors, and administrations so the arrangement doesn’t unnecessarily devour accessible assets.
For instance, some Salesforce Lightning Platform patterns have arrangements that are ideal for little volumes of data. The ideal integration design these arrangements adjust to is Remote Process Invocation—Request and Reply. In this example, the framework sends a little (or single) exchange and requires an answer. This example is extraordinary for little exchanges. Notwithstanding, there are lead representative cutoff points and permit allotments to consider.
There are different patterns that turn out better for mass data handling like Batch Data Replication. Heroku Connect is accessible in this example choice. This choice turns out best for snatching a lot of data immediately without surpassing cutoff points. Realizing the volume is significant while considering as far as possible accessible for the plan.
The timing and recurrence of correspondence are significant while assessing integration arrangements. Consider whether you need the framework to send the correspondence in close ongoing or to handle it later in a bunch. The arrangement you execute decides the timing of the correspondence.
There are two sorts of integration modes: offbeat and simultaneous.
Simultaneous correspondence implies a customer sends a solicitation to the worker and hangs tight for the reaction prior to giving another solicitation. For instance, the Remote Process Invocation—Request and Reply integration design is a coordinated correspondence. An application communicates something specific and sits tight for an answer prior to continuing.
Offbeat correspondence implies the framework doesn’t hang tight for an answer prior to continuing. The application communicates something specific and the framework returns an answer when the assets are free. The framework that sent the first message can keep sending messages without hanging tight for an answer. Handling the return message is controlled independently.
Security is a significant thought when planning an integration arrangement. Your plan ought to incorporate viewpoints like user personality, data concealing, and PII stockpiling as a feature of your integration technique. The General Data Protection Regulation (GDPR) is a guideline in EU law on data security and protection in Europe. Most US-based organizations have received this law as a best practice for their business.
Integration patterns that follow the course Salesforce → System advantage the most from consolidating Shield Platform Encryption into their plan. Safeguard Platform Encryption utilizes a blend of a one-of-a-kind occupant secret you keep up and an expert mystery that is kept up by Salesforce. Together they make an extraordinary data encryption key. Survey the Salesforce Shield Platform Encryption Implementation Guide to learn how to join it into your plan.
Blunder Handling and Recovery
There is an assortment of mistakes that happen in an integration. Blunders incorporate framework edges, (for example, lead representative cutoff points and API designations), business measure mistakes (when a solicitation disregards business rules), and user approval and confirmation issues. It’s imperative to incorporate a blunder dealing with and recovery technique as a component of the general arrangement.
At the point when a blunder happens (special cases or mistake codes are gotten back to the guest), the guest oversees the blunder taking care of. For instance, when a mistake message showed on the end user’s page or logged to a table requires further activity.
Changes aren’t focused on Salesforce until the guest gets an effective reaction. For instance, the request status isn’t refreshed in the database until a reaction that demonstrates achievement is gotten. In the event that vital, the guest can retry the activity.
Correspondence across various frameworks presents the danger of idleness and shakiness when out of sync. Every arrangement depends on various conditions across frameworks. These conditions incorporate innovation prerequisites, (for example, administrations utilized), data type necessities (date, number, text conveyed), or cooperation style (offbeat versus simultaneous and timing) to give some examples.
Segments in an approximately coupled arrangement can be changed out should a necessity or reliance change. For instance, informing is an inexactly coupled arrangement when used in an offbeat correspondence. Firmly coupled arrangements don’t have a lot of adaptabilities to be modified without updating the integration technique. When settling on arrangement alternatives, pick the inexactly coupled choice to lessen the danger of conditions breaking.
In the following unit, you practice assessing a Salesforce Lightning Platform integration design utilizing every one of the instruments you’ve learned so far in this module.
B) Which Lightning Platform integration pattern follows the System → Salesforce direction?
- What should you study to learn how to integrate data across Salesforce Service Cloud orgs and Commerce Cloud orgs?
- Which is the best solution to use when implementing the Remote Process Invocation—Request and Reply pattern?
Recommended Programming Language