Integration Patterns and Architecture

Headless Salesforce & APIsIntegration Patterns and ArchitectureApply Salesforce's integration pattern catalog (request-reply, fire-and-forget, batch sync, remote call-in, UI updates, data virtualization) using the right platform features. Covers Salesforce Connect, MuleSoft API-led connectivity, reliability (idempotency, retries, dead letters), system-of-record decisions, integration security and monitoring, with an end-to-end ERP and e-commerce case study.Advanced · about 100 minutesWhat you will learn

Map an integration requirement to one of the six Salesforce integration patterns and the platform features that implement it

Choose between synchronous and asynchronous designs, and between middleware and point-to-point

Implement reliable outbound integrations with idempotency keys, retries with backoff, and dead-letter handling in Apex

Virtualize external data with Salesforce Connect, including a custom adapter built with the Apex Connector Framework

Decide system of record and master data ownership, and use external IDs for cross-system keys

Secure and monitor integrations: least-privilege integration users, Named and External Credentials, certificates and mTLS, alerting

Contents

Four questions that pick the pattern

The pattern catalog

Salesforce Connect and external objects

MuleSoft and API-led connectivity

Synchronous vs asynchronous trade-offs

Reliability: idempotency, retries and dead letters

Data ownership, system of record and master data

Integration security

Monitoring and alerting

Case study: ERP + e-commerce + Salesforce

Integration architecture review checklist

Best practices

Common pitfalls

Hands-on exercises

Key takeaways