IntegrationAdvancedsalesforce-connectodatavirtualization
Implement Salesforce Connect for external data virtualization
Real World Scenario
Inventory levels live in external SQL database. Team debates copying into Salesforce nightly vs real-time lookup.
Expected Answer
• Salesforce Connect OData or custom adapter for read-heavy external lookups
• Accept latency and availability dependency on external system
• Not suitable for high-volume triggers querying external per record
• Cache frequently accessed items via Platform Cache wrapper Apex if needed
• Fallback behavior when external org unavailable—show last known or block
• Compare TCO Connect vs replicate to Custom Object via ETL
• Security: OAuth to external and row-level filter at source
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Salesforce Connect OData or custom adapter for read-heavy external lookups. Accept latency and availability dependency on external system. Pick based on your integration pattern and team capability. Connect is federation not replication—architects validate query volume and latency before virtualizing LDV lookups. Optimize for scale and operational observability.
Architect Perspective
Connect is federation not replication—architects validate query volume and latency before virtualizing LDV lookups.