Salesforce Integration Pattern Overview

Integration Pattern
Overview
SalesforceCodex.com 1

About Me
Dhanik Lal Sahni
Technical Architect
Conduent Business Solution
Certified Application Architect
Twitter : @dhaniksahni
Blog : salesforcecodex.com

Session 1-Agenda
• Provided an integration scenario, describe requirements and
issues that the Architect must consider to select the right pattern
(Layer, Timing, Direction, and Volume).
• In a customer scenario containing business requirements,
summarize which implementation pattern will achieve those
goals.
• Compare and contrast the advantages and drawbacks (design
trade-offs) of using various patterns, such as Remote Process
Invocation—Request and Reply, Remote Process Invocation—Fire
and Forget, Batch Data Synchronization, Remote Call-In, and UI
Update Based on Data Changes.
28%
17%
15%
10%
15%
10%
5%
Integration Architecture
Designer Exam
1 2 3 4 5 6 7
Salesforce Integration Patterns: 17%

What is Integration?
Integration is the process of connecting different sub-
systems or components into a single larger system that
functions as one.

Why we need Integration?
1. A 360-degree view of customer information
2. Better data flow
3. Faster business processes
4. Improved efficiency across teams
5. Improved security
6. Reduced costs

Types of Integration Pattern
Type Description
Remote Process Invocation—
Request and Reply/Response
Salesforce invokes a process on a remote system, waits for completion of that process,
and then tracks state based on the response from the remote system.
Remote Process Invocation—
Fire and Forget
Salesforce invokes a process in a remote system but doesn’t wait for completion of the
process. Instead, the remote process receives and acknowledges the request and then
hands off control back to Salesforce.
Batch Data Synchronization Data stored in Lightning Platform is created or refreshed to reflect updates from an
external system, and when changes from Lightning Platform are sent to an external
system. Updates in either direction are done in a batch manner.
Remote Call-In Data stored in Lightning Platform is created, retrieved, updated, or deleted by a remote
system
UI Update Based on Data
Changes
The Salesforce user interface must be automatically updated as a result of changes to
Salesforce data
Data Virtualization Salesforce accesses external data in real time. This removes the need to persist data in
Salesforce and then reconcile the data between Salesforce and the external system.

Integration Pattern Approach
Data Integration
Process Integration
Virtual Integration
Address the requirement to synchronize data that resides in two or
more systems so that both systems are in sync.
• Address the need for a business process to leverage two or
more applications to complete its task.
• Triggering application has to call across process boundaries to
other applications
• Address the need for a user to view, search, and modify data
that’s stored in an external system
• Triggering application has to call out to other applications and
interact with their data in real time

Pattern Selection Aspects
Source/Target
Timing
Specifies the style of integration: Process, Data, or Virtual
• Synchronous—Blocking or “near-real-time” requests
• Asynchronous—Non-blocking, queue, or message-
based requests
Type
Specifies the requester of the integration transaction along with
the target(s) that provide the information.

Pattern Selection Matrix
Source/Target Process
Integration
Data
Integration
Virtual
Integration
Synchronous Asynchronous Patterns to Consider
Type Timing
  Remote Process
Invocation- Request n
Response
Salesforce –>
Other System


Remote Process
Invocation- Fire n Forget


Remote Process
Invocation- Request n
Response
UI Update Based on
data changes
 Data Virtualization

Pattern Selection Matrix
Source/Target Process
Integration
Data
Integration
Virtual
Integration
Synchronous Asynchronous Patterns to Consider
Type Timing
  Remote Call-in
Other System
–> Salesforce


Remote Call-in



Remote Call-In
Batch Data
Synchronization

Classify Integration API

Integration Layers?

Factors which will affect Pattern
Same
Transaction
Synchronous/
Asynchronous
Message Size
Same Transaction
Any operation required on
response from remote
system?
Synchronous/Asynchronous
Process need to be done in real time
or near real time?
Guaranteed
Delivery
Contract First
Declarative
Preferred
Message Size
Message size is small or
big?
Contract First Integration
Remote system support
Salesforce contract?
Guaranteed Delivery
What if external system is down?
Declarative Preferred
Integrate with Standard or custom
code?

Remote Process Invocation—Request and Reply
Problem : When an event occurs in Salesforce, how do you initiate a process in a remote
system, pass the required information to that process, receive a response from the remote
system, and then use that response data to make updates within Salesforce?
Solution Fit/Rating Pattern Description
External Services Best
Enhanced External Services best fit if
1. External Service is REST API
2. Request and response definitions
contain primitive data types
3. Transaction can initiate from Flow
4. Transaction doesn’t risk exceeding
the synchronous Apex governor
limits

Remote Process Invocation—Request and Reply
Salesforce Lightning or VF Page Best
• Process can initiate form custom UI
• Salesforce enables us to consume a WSDL and generate a
resulting proxy Apex class.
• It provide HTTP service to do REST API operations.
• Full Control of logic
Trigger Suboptimal
1. Apex triggers to perform external callout on data changes
2. Call should be asynchronous
3. Not suited for this. Can be used In fire n forget calls.
Batch Apex job Suboptimal
1. Make calls to a remote system from a batch job
2. Given batch has limits to the number of calls

Remote Process Invocation—Fire and Forget
Problem : When an event occurs in Salesforce, how do you initiate a process in a remote
system and pass the required information to that process without waiting for a response
from the remote system?
Process-driven platform events Best
1. Publish Platform Event when remote process need to be invoked
from an insert or update event
2. Can process same event to multiple systems
3. Use Flow or process builder to process event
Customization-driven platform
events
Good
1. When point n click not works then use custom platform events
2. Publish and consume platform events by using Apex or an API.
Workflow-driven outbound
messaging
Good
1. Use when remote process is invoked from an insert or update
event.
2. Messages are sent asynchronously
3. Contract First Integration
4. Solution becomes a “first-mile” guarantee of delivery.
5. Retry if successful response is not received

Remote Process Invocation—Fire and Forget
Salesforce Lightning or VF Page Best
• Process can initiate form custom UI
• User interface-based scenarios, but does require customization
• Salesforce enables you to consume a WSDL and generate a
resulting proxy Apex class.
• It provide HTTP service to do REST API operations.
Trigger Suboptimal
1. Apex triggers to perform external callout on data changes
2. Call should be asynchronous
Batch Apex job Suboptimal
1. Make calls to a remote system from a batch job
2. Given batch has limits to the number of calls

Batch Data Synchronization
Problem : How do you import data into Salesforce and export data out of Salesforce, taking
into consideration that these imports and exports can interfere with end-user operations
during business hours, and involve large amounts of data?
Salesforce Change Data Capture Best
• Change Data Capture publishes change events, which represent
changes to Salesforce records.
• Receive near-real-time changes of Salesforce records
ETL Tool Best
1. Connect to system, extract data and transform in required format
2. Upload data using Bulk API
Remote Call-in Good
System can call each other whenever data is changed.

Remote Call-in
Problem : How does a remote system connect and authenticate with Salesforce to notify
Salesforce about external events, create records, and update existing records?
1. SOAP APIs can be used by clients to
• Publish events to notify your Salesforce org
• Query data in your org
• Create, update, and delete data
• Obtain metadata about your org
• Run utilities to perform administrative tasks
2. Valid login session is required.
3. Provides Enterprise WSDL and Partner WSDL for
communication
4. Client wait for response
Best

Remote Call-in
Problem : How does a remote system connect and authenticate with Salesforce to notify
Salesforce about external events, create records, and update existing records?
REST APIs can be used by clients to
• Publish events to notify your Salesforce org
• Query data in your org
• Create, update, and delete data
• Obtain metadata about your org
• Valid login session is required.
• Client wait for response
• Each record treated as separate transaction
• For bulk data operations (more than 500,000
records), use the REST-based Bulk API.
Best

Remote Call-in
• Apex class can be used as web service method
• Use when full transactional support is
required
• Custom Logic is required
Apex web
services
Apex REST
services
• Apex class exposed as REST URI
• Use for multiple updates in same transaction
• No need to consume WSDL
Bulk API
• REST based API to support larger data sets
• Support query, update, delete records large
no of records asynchronously
Sub
optimal
Optimal
Sub
optimal

UI Update Based on Data Changes
Problem : When an event occurs in Salesforce, how can the user be notified in the
Salesforce user interface without having to refresh their screen and potentially losing work?
Salesforce Streaming API is best for this use case.
A JavaScript-based implementation of the CometD required

Data Virtualization
Problem : How do you view, search, and modify data that’s stored outside of Salesforce,
without moving the data from the external system into Salesforce?
Solution Fit/Rating
Salesforce Connect Best
• Use Salesforce Connect to access data from external sources, along
with your Salesforce data
• Salesforce Connect maps data tables in external systems to external
objects in your org.
• Salesforce Connect uses a live connection to external data to always
keep external objects up-to-date.
Request and Reply Suboptimal
1. Use Salesforce web service APIs to make ad-hoc data requests to
access and update external system data.
2. Use Salesforce SOAP API.
3. A custom Visualforce page or button initiates an Apex SOAP callout
in a synchronous manner

Pattern Summary
Request &
Response
Fire & Forget UI Update
Batch
Integration
Remote Call-In UI Update
Data
Virtualization
Salesforce waits
for response
Response not
needed
immediately
Data
Synchronization
between two
systems
External System
Calling Salesforce
Refresh UI on
data changes
Show live
external data

salesforcecodex.com 25
Keep Exploring. Keep Learning.

Salesforce Integration Pattern Overview

Recommended

More Related Content

What's hot (20)

Similar to Salesforce Integration Pattern Overview (20)

Recently uploaded (20)

Salesforce Integration Pattern Overview