Successfully reported this slideshow.

Combining EDA & API-led Connectivity through MuleSoft for integrating Salesforce with multiple ERPs, Marcelo Caponi

0

Share

1 of 35
1 of 35

Combining EDA & API-led Connectivity through MuleSoft for integrating Salesforce with multiple ERPs, Marcelo Caponi

0

Share

Download to read offline

Description

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.

Transcript

  1. 1. Combining EDA & API-led Connectivity through MuleSoft for integrating Salesforce with multiple ERPs Marcelo Caponi
  2. 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
  3. 3. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  4. 4. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  5. 5. #CD22 IT today (80% of time integrating, not innovating)
  6. 6. #CD22 IT capacity can’t keep peace with today’s demands
  7. 7. #CD22 Current responses are insufficent Not Sustainable Exacerbates the situation Not sufficient
  8. 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
  9. 9. #CD22 Self-service API Portals
  10. 10. #CD22 API-led connectivity
  11. 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
  12. 12. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  13. 13. #CD22 Event-Driven Architecture (EDA) Event Bus Event Consumer Event Consumer Event Consumer Event Producer Event Producer
  14. 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. 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. 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. 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. 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
  19. 19. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  20. 20. #CD22 Platform Events + Salesforce Event Bus Publishing Events APEX Flows LWC APIs … Transactional Publish After Commit Non-Transactional Publish Immediately Retention Period High Volume – 72 Hours Standard Volume – 24 Hours
  21. 21. #CD22 Platform Events
  22. 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)
  23. 23. #CD22 Change Data Capture (CDC)
  24. 24. #CD22 Change Data Capture (CDC)
  25. 25. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  26. 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. 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. 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
  29. 29. #CD22 Accounts Integration Design
  30. 30. #CD22 Accounts Integration Design
  31. 31. #CD22 Accounts Integration Design
  32. 32. #CD22 Accounts Integration Design
  33. 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
  34. 34. #CD22
  35. 35. Thank you! #CD22

Description

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.

Transcript

  1. 1. Combining EDA & API-led Connectivity through MuleSoft for integrating Salesforce with multiple ERPs Marcelo Caponi
  2. 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
  3. 3. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  4. 4. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  5. 5. #CD22 IT today (80% of time integrating, not innovating)
  6. 6. #CD22 IT capacity can’t keep peace with today’s demands
  7. 7. #CD22 Current responses are insufficent Not Sustainable Exacerbates the situation Not sufficient
  8. 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
  9. 9. #CD22 Self-service API Portals
  10. 10. #CD22 API-led connectivity
  11. 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
  12. 12. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  13. 13. #CD22 Event-Driven Architecture (EDA) Event Bus Event Consumer Event Consumer Event Consumer Event Producer Event Producer
  14. 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. 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. 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. 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. 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
  19. 19. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  20. 20. #CD22 Platform Events + Salesforce Event Bus Publishing Events APEX Flows LWC APIs … Transactional Publish After Commit Non-Transactional Publish Immediately Retention Period High Volume – 72 Hours Standard Volume – 24 Hours
  21. 21. #CD22 Platform Events
  22. 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)
  23. 23. #CD22 Change Data Capture (CDC)
  24. 24. #CD22 Change Data Capture (CDC)
  25. 25. #CD22 Agenda API-led Connectivity Event-Driven Architecture (EDA) EDA in Salesforce EDA & API-Led (SFDC <-> ERP)
  26. 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. 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. 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
  29. 29. #CD22 Accounts Integration Design
  30. 30. #CD22 Accounts Integration Design
  31. 31. #CD22 Accounts Integration Design
  32. 32. #CD22 Accounts Integration Design
  33. 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
  34. 34. #CD22
  35. 35. Thank you! #CD22

More Related Content

More from CzechDreamin

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

×