Salesforce ArchitectureArchitect (Hardest)integrationprinciplesarchitecture
Define integration architecture principles for Salesforce hub
Real World Scenario
CTO requests documented integration principles before approving 12 new SaaS connectors this quarter.
Expected Answer
• API-first: prefer platform APIs over UI automation or database scraping
• Async by default for cross-system writes; sync only with latency budget
• Idempotency and correlation IDs mandatory on all inbound interfaces
• System of record declared per entity attribute—not assumed Salesforce
• Event-driven preferred over polling for high-change data
• No point-to-point spaghetti: hub or iPaaS for 3+ system connections
• Security: least privilege integration users and secrets in vault
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: API-first: prefer platform APIs over UI automation or database scraping Also consider: Async by default for cross-system writes; sync only with latency budget In practice: Idempotency and correlation IDs mandatory on all inbound interfaces Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Principles enable fast decisions—without them every team reinvents integration architecture poorly.