Event-Driven Architecture (EDA) has been widely adopted for companies looking to accelerate their digital transformation. These companies realized that batch-based, point-to-point Integrations slow down the business and leave a technical debt. EDA improves the ability to react to changes in real-time and improves the overall customer experience. API-led connectivity approach unlocks data through APIs allowing companies to create a composable business. In this session, I will share how to integrate Salesforce with multiple ERPs by combining EDA & API-led Connectivity through MuleSoft.
%in ivory park+277-882-255-28 abortion pills for sale in ivory park
Combining EDA & API-led Connectivity through MuleSoft for integrating Salesforce with multiple ERPs, Marcelo Caponi
1. Combining EDA & API-led Connectivity through
MuleSoft for integrating Salesforce with multiple ERPs
Marcelo Caponi
2. #CD22
● I’ve been around Integrations for the last 15 years
● Started with Salesforce in 2012
● Technical Architect at Pernod Ricard HQ (Paris)
● Speaking at Several Dreamin from 2020
● MuleSoft Certified Integration Architect (MCIA)
● Blogger at
About me
8. #CD22
● Expose data and business
capabilities for reuse
● Productized and designed for
ease of consumption
● Easily managed for Security,
Scalability and Performance
● Discoverable and accessible
through self-service API Portals
APIs as standard building blocks
11. #CD22
Application Network
● Emerges bottom-up
● Self-Service
● Provides visibility, security, and
governability at every API Node
● Is recomposable: It bends, not breaks
● Built for change
14. #CD22
● Events represents Facts of Information
● Facts already happened
● Facts are immutable
● You can listen the facts if you want to
What is an Event?
15. #CD22
Event Types
• Intent
• Direct to a Single Address
• Expect an action to be taken for
someone
• Side-effects
• Imperative-Tense
CreateOrder, ShipProduct
Commands
• No Intent
• Broadcast communication
• No expectation
• Depends on the consumer
• Past-Tense
OrderCreated, ProductShipped
Events
vs.
16. #CD22
Modeling Events
“When you start modeling Events, it forces you to think about the
behavior of the system. As opposed to thinking about the
structure of the system.”
Greg Young
17. #CD22
● Overall Integration Strategy
● Support for legacy systems
● Structural changes to messages
● Lack of visibility between publishers and subscribers
● Performance bottlenecks
Challenges to consider when implementing EDA
18. #CD22
● Real-time notifications
● Paralell processing
● High-volume reads
● Sending the same data to different systems
● Frequently introducing new systems or devices into an IT landscape
● IoT devices
● Mobile devices and systems that may be offline when changes occur
When should you use EDA?
https://architect.salesforce.com/design/decision-guides/event-driven
22. #CD22
• Special type of Platform Events
• Published automatically by Salesforce in real-time when records change
• Events published for: create, update, delete, and un-delete operations
• Events are stored up to 3 days
• Asynchronous Triggers can be implemented, only after insert
(Events are immutable)
Change Data Capture (CDC)
26. #CD22
• Retail Execution Mobile App connected to Salesforce
• Salesforce Single Org with the Backend of the Mobile App
• Application rolled-out to more than 20 affiliates
• Each affiliates manage their own ERP (JDE, NAV, SAP)
• Account Integration is required in almost real time
Scenario - Integrating Salesforce with 3 ERPs
27. #CD22
• Invoke every ERP with outbound calls from APEX
• We have to code all transformations from Objects to APIs
by country (different formats: SOAP, JSON, v1, v2, etc.)
• Error Handling, Retries, Security, and so on.
• Point-to-point Integration
• APEX is not a Middleware! --> Technical Debt
Accounts Integration Design – First Approach
9.1
9.2
28. #CD22
Principles
• Keep Salesforce “clean” with no ERP dependency
• The Integration is completely transparent for Salesforce
Opportunity to
• Introduce a Middleware (e.g. MuleSoft)
• Design an “Event-Driven” solution combining API-led connectivity
Accounts Integration – The “right” approach
33. #CD22
• Event-Driven Architecture is a good option for decoupling applications
(producers and consumers)
• Salesforce offers out of the box powerful capabilities like CDC
• Platform Events can be defined for more flexibility (payload, publishing)
• API-led connectivity provides an approach for creating Application
Networks promoting reusability
• EDA & API-led connectivity can complement each other for building
robust Integration Architectures
Recap