Salesforce Integration Architecture Variants

Overview

Produce a falsifiable architecture decision that explains why one interaction pattern fits each use case and which tradeoffs remain.

Prerequisites

• Use cases, business invariants, sources of truth, consumers, latency, volume, ordering, consistency, and recovery needs
• Org products, APIs, events, limits, identities, data classes, residency, retention, support, and existing platforms
• Security, operability, cost, skills, vendor, migration, lock-in, disaster recovery, and change-control constraints

Tool Discipline

Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts.

Current Contract

Salesforce documents remote process, batch, data synchronization, and event integration patterns. Direct REST, composite, bulk, Pub/Sub or CDC, middleware, event relay, and replicated read models differ in coupling, consistency, capacity, and recovery.