salesforce-architecture-variants

# Salesforce Architecture Variants ## Overview Three validated architecture blueprints for Salesforce integrations: Direct API (simple), Event-Driven (scalable), and Middleware/iPaaS (enterprise). Each pattern addresses different scale, latency, and complexity requirements. ## Prerequisites - Understanding of your data volume and sync frequency requirements - Decision on unidirectional vs bidirectional data flow - Knowledge of Salesforce edition (affects available features like CDC) ## Variant A: Direct API Integration (Simple) **Best for:** MVPs, < 50K records/day, single-direction sync ``` ┌─────────────┐ jsforce ┌─────────────┐ │ Your App │ ──── REST API ──▶ │ Salesforce │ │ (Node.js) │ ◀── SOQL/SOSL ── │ Org │ └─────────────┘ └─────────────┘ Data flow: - App queries SF via SOQL (polling or on-demand) - App writes to SF via sObject CRUD - Scheduled cron for periodic sync ``` ### Key Characteristics - Single jsforce connection per process - Polling-based reads (cron schedule) - Direct REST writes - In-memory or Redis caching for describe/metadata - Suitable for: internal tools, admin dashboards, simple data sync ### Code Pattern ```typescript // Cron-based sync — runs every 15 minutes import cron from 'node-cron'; cron.schedule('*/15 * * * *', async () => { const conn = await getConnection(); // Fetch recently modified accounts const accounts = await conn.query(` SELECT Id, Name, Industry, AnnualRevenue FRO...