Integration Patterns and Designs
In this post will learn Salesforce Integration Patterns with explanations, and with example and security considerations, interview questions, and certification quiz questions. Discover when to use Request and Reply, Fire and Forget, Batch Data Synchronization, Remote Call-In, Data Virtualization, High-Frequency Data Replication, and Publish/Subscribe patterns to build scalable Salesforce integrations.
6/7/20262 min read
What Are Integration Patterns?
Integration Patterns are proven ways to connect different systems and applications so they can work together smoothly.
First, think of them as ready-made solutions that architects and developers use to solve common integration problems instead of creating a new solution from scratch every time.
Example
Salesforce for customer management(Create Case in salesforce)
SAP for billing and create order or product
A payment gateway for payments.
These systems need to exchange information. Integration patterns help decide how they should communicate.
Why Are Integration Patterns Important?
Integration patterns will help us to understand the complexity of the system and when and where which integration pattern should show.
Connect systems efficiently
Follow best practices
Reduce development time
Improve reliability
Avoid reinventing the wheel
How to Evaluate an Integration Pattern
When reviewing an integration pattern:
Read the business scenario and understand the problem and review the recommended solution.and check whether it will achieve your requirement.
Types of Integration Initiatives
Before selecting the pattern, identify the type of integration which types of Integration initiatives we need
1. Application Integration
Focuses on connecting applications and extending functionality.
API integrations(Call API)
Salesforce Flow calling external systems
UI triggered actions
Example: A Salesforce user clicks a button to create an order in SAP.
2. Data Integration
Focuses on moving and synchronising data between two systems.
Data migration(Data migration from one system to another system)
Data synchronisation(Data sync in bulk from one system to another system
Example: Update Salesforce data automatically in an ERP system.
3. Process Integration
Focuses on connecting business processes across multiple systems.
Event-driven processes
Cross-system workflows
Automated business transactions
Example: When an order is approved in Salesforce, a shipping process starts in another system.
Security Considerations
Security is critical when integrating systems.
Common security requirements include:
Single Sign-On (SSO)
SAML Authentication
Data Encryption
GDPR Compliance
Example
A company stores customer credit card information in Salesforce. To protect sensitive data, they can use Salesforce Shield Platform Encryption, which encrypts the data and helps meet GDPR requirements.
Salesforce Lightning Platform Integration Patterns
Below are the most common Salesforce integration patterns.
1. Remote Process Invocation – Request and Reply
Salesforce sends a request to another system and waits for a response.
Example
A user creates an order in Salesforce and sends the order to SAP and waits for SAP to return the order status.
2. Remote Process Invocation – Fire and Forget
Salesforce sends a request but does not wait for a response it call fire and forget
Example
After an order is placed, Salesforce sends a notification to another system . Salesforce continues working without waiting for confirmation.
3. Synchronization
Data is synchronized in groups (batches) at scheduled times.
Example
Every night, Salesforce exchanges customer data with an ERP system and as well as with other system
4. Remote Call-In
An external system calls Salesforce APIs to create, read, update, or delete records.
Example
A CSP application creates customer records directly in Salesforce using API.
5. Data Virtualization
Salesforce accesses external data in real time without storing it.
Example
Salesforce displays product inventory directly from an ERP system but does not store it in the salesforce system.
6. High-Frequency Data Replication
source system asynchronously replicates data to a target system in near–real time at high scale.
Example
Thousands of IoT sensor records are continuously copied into Salesforce.
7. Publish/Subscribe Pattern
Salesforce publishes events and multiple systems can subscribe to them.
Example
When a customer record changes:
Billing system receives the event
Analytics system receives the event
Quick Exam & Interview Questions
Q1. Which pattern is used when Salesforce sends a request and waits for a response?
Answer: Remote Process Invocation – Request and Reply
Q2. Which pattern allows Salesforce to send a request without waiting for completion?
Answer: Remote Process Invocation – Fire and Forget
Q3. Which pattern is best for nightly data updates?
Answer: Batch Data Synchronization
Q4. Which pattern lets external systems create records in Salesforce?
Answer: Remote Call-In
Q5. Which pattern allows Salesforce to access external data in real time without storing it?
Answer: Data Virtualization